pleasenonosspammkallal@msn.com (Albert D. Kallal) wrote in
<3InOb.152288$X%5.49959@pd7tw2no>:
[color=blue]
>The user fix to restore performance back is to make sure that you
>keep a connection to a table opened at all times FROM the front
>end, to the back end.
>
>Windows XP has a huge increase in file security stuff, . ..[/color]
It does? What exactly? NTFS 5 was introduced with Win2K, so I don't
know of anything added in WinXP.
Certainly MS reorganized the user interface and altered the default
security configuration somewhat, but I don't know of any "huge
increase in file security."
[color=blue]
> . . . and thus
>anything that deletes, or creates a file TAKES a very long time![/color]
Er, on what basis do you make this statement? I see no such thing
happening in any versions of Windows.
[color=blue]
>Since ms-access constantly tries to delete and create the locking
>file, then a huge performance hit takes place, as now ms-access is
>simply reduced to the speed of the system to create/delete that
>locking file.[/color]
I think this is simply not true.
[color=blue]
>So, keep a persistent connection open, and things will perform
>like before. In fact, you will generally find things performance
>EVEN better when you do this.[/color]
There as *always* been a performance drain from repeatedly
deleting/recreating the LDB file, and the performance hit has not
been changed by the OS.
[color=blue]
>I have run a97 on some new XP computers networks, and it absolute
>screams....
>
>So, when the application start-ups, just have it open a form to
>some table in the back end, and either minimize that form, or even
>set it invisible. You can also open a global reocrdset in code
>also. Regardless, anything that forces the backend to stay opened
>to the front end will fix this problem.[/color]
For what it's worth, I've tried this kind of thing in a few apps
and never seen any discernable effect on performance whatsoever.
--
David W. Fenton
http://www.bway.net/~dfenton
dfenton at bway dot net
http://www.bway.net/~dfassoc 
