Performance 03 FE and 97 BE

[JimInKS]

I have an application implemented in MS Access that we use for scheduling. BE Database is only around 6MB at the moment. With Access 97 database for both FE and BE it is fast enough that there is no perceptible delay in operations. When I convert the FE to Access 03 and leave the BE as 97 performance drops drastically.

I have watched the windows network performance monitor and with a 100MB connection I see small blips of a few percent network use when both FE and BE are 97 db's. When the FE is 03 I get spikes up to around 25%. Obviously the 03 FE is not optimizing the BE accesses like the 97 FE. If I convert the BE to 03 format, performance is much better (though still slower marginally slower than 97).

Maybe I should just bite the bullet and upgrade everyone to 03, but Access 97 has been rock solid for years and everyone likes it better because of the great performance.

I have tried setting the "Subdatasheet property" on BE tables per MS Q261000 to no effect. Also tried setting Access 03 to use MS DAO 3.5 object library like Access 97 was using. Neither seemed to have any effect.

Any Ideas or suggestions?

 

[hermanlaksko]

The Access 97 edition was properly the best access ever, but it had one serious flaw - it would crash from time to time.

The 200x editions was taken over by ms-programmers and userfreindlyness was, and is still being squeezed out of it, however the database as such, is much more sturdy.

But as I understand you, you are not experiencing any problems with your current setup, your users also seem to prefer A97 and your app's. performance is dropping when changed to A2x, so why change, I wonder.

Herman
Say no to macros

 

[JimInKS]

I guess I just felt the need to get into the current Millennium

I tried to switch when Office XP came out. I even bought the developer edition. But, after awhile it drove me crazy and I went back to 97.

I have several MS Access 97 apps that have been running for over 10 years, used every day, mostly by a small number of users (ie < 10) and have NEVER had a database file corrupted after I learned of the "lanman fix".

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"CachedOpenLimit"=dword:00000000
"EnableOplocks"=dword:00000000

 

[hermanlaksko]

I would - if I had to go from 97 to 200x keep my FE/BE in version 2000 and not use 2003.

I am, however, sure that you will find that your app. will perform/execute slower.
But what you trying to achieve, besides getting your app's into the current millennium is still unclear to me ;-)
The way ms is paying ther programmers is by the so called "k-logs" system ... so good programming is OUT, sloppy 1000-lines-that-do-nothing is IN.

The "lanman fix" is interesting and news to me what is the stoty behind this ?

Herman
Say no to macros