[RBASE-L] - RE: What's up with this?

[Dennis McGrath]

Access will suffer the same problems on an MS server, since it is a file server db just like RBASE (I believe it was a rip off of RBASE to begin with!!!) There is a considerable amount of server tuning instructions out there to try to help alleviate the problem with file server dbs, but the MS security model generates lots of network traffic due to the fact that it checks your access rights to each and every file every time you access them over the network.   Novell of old had you log in , figured out your access rights, and screamed forward from there. It's disk caching was awesome too.    Better to avoid any MS caching of DB files!!!  Brain dead.   When we get to Client-Server, these issues will largely go away because all access to the db is by code running on the server and thus the db files are "local"   Dennis McGrath         From: rbase-l@rbase.com [mailto:[EMAIL PROTECTED] On Behalf Of Castanaro, Bob Sent: Monday, July 10, 2006 12:55 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: What's up with this? Does anyone have any experience on this issue with Access?  OK, the DREADED Access.  Does Access have the same speed issues, or is there some trick they (MS) are not sharing that optimizes the MS servers?   For a small office, this will continue to be an issue and will be a problem for R:Base.  For a large installation, I'm sure the RB Client -Server will solve it.  Novell really blew it a few years back.  It was clean, stable and efficient.  R:base screamed on it.  They just had no clue how to market, and were way behind on a GUI interface.  Look how they bumbled Word Perfect, still the best word processor ever.   BC From: rbase-l@rbase.com [mailto:[EMAIL PROTECTED] On Behalf Of Javier Valencia Sent: Monday, July 10, 2006 1:41 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: What's up with this? Emmitt: This is a nice checklist; however, as a way of background, my client has a Novell server and they were experiencing some delays (turned out to be a problem with R:Base, now fixed). We tried switching the client cards form auto to full duplex and the response dropped to a crawl, we set the cards back to auto and the performance improved dramatically. I am nor sure if this is typical but it would be wise to test it both ways and see if how performance is affected. Javier,   Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ======================================================   -----Original Message----- From: rbase-l@rbase.com [mailto:[EMAIL PROTECTED]On Behalf Of Emmitt Dove Sent: Monday, July 10, 2006 12:17 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: What's up with this?   Lee, The problem is a Microsoft thing.  Any time on an MS network with the database on an MS server, more than one user experiences slowdown.  To combat this, there are a few steps to take: 1. Use a gigabit link between all your machines.  2. Use a switch downstream from the router. 3. Try to use hardware that supports full duplex.  Check your cards to see if they're operating full duplex, and if not (and set to AUTO), try forcing full duplex. 4. Use quality cables. 5. Make certain each user has scratch files set to their local drive. 6. Run with STATICDB ON. 7. Make certain the box holding the files is set to optimize for background services not applications. 8. Don't use the box holding the files for anything else. 9. Don't use peer-to-peer; install a domain controller (not on the file server). 10. Install R:Base locally on each client. 11. Run, don't walk, to 7.5, Windows not DOS. Now, these are all in the nature of suggestions, but are things we've found improve the responsiveness. Have you experienced the same types of difficulties when employing your applications in a network scenario?  What do the "big boy" clients do to avert this issue?   Thanks to all!   Lee   Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 37 Sybil Ave Branford, CT  06405 (203) 643-8022 [EMAIL PROTECTED] [EMAIL PROTECTED]