Problems with Access/Windows 2003 Server?

[Guest]

After "upgrading" an NT4 server to Windows Server 2003 Standard R1, it now
takes 20 - 30 seconds to open a small (1 mb) Access mdb file. The same file
can be copied from the server instantly. Client PC's have not changed, only
the server changed, never a problem with the old NT4 server. One the file is
opened, everything else works normally.

Anyone experience this problem?

Thanks

 

[dbahooker]

Yes.

Don't use MDB for anything; it is completely obsolete.

Use SQL Server, and 'Access Data Projects' and you won't subject your
end users to this type of pain point.

-Aaron
ADP Nationalist

 

[William Hindman]

....Access mdbs work fine on Win2003 Server using either Dao or ado ...they
are not "obsolete" regardless of bandwidth wasting ego posts to the contrary


....assuming the accuracy of your statement that nothing was changed on the
workstations, there is nothing inherent in any version of Access that would
cause this type of problem with W2K3Server ...thus I'd go back over your
server configuration to identify where/why the abnormal delays are occurring
....I'd look first at your hardware ...NT4 would run successfully on a lot
less memory than 2003 ...and high memory allocation would cause the symptoms
you describe (as would numerous other things) ...but that is the first place
I'd look.

William Hindman

 

[Tony Toews]

After "upgrading" an NT4 server to Windows Server 2003 Standard R1, it now
takes 20 - 30 seconds to open a small (1 mb) Access mdb file. The same file
can be copied from the server instantly. Client PC's have not changed, only
the server changed, never a problem with the old NT4 server. One the file is
opened, everything else works normally.

One possibility is that your antivirus software on the server is set
to scan *.MDBs. If so exclude MDBs and MDEs.

Does this happen for a the first user accessing the MDB or the second
and subsequent users? If so this is the LDB locking problem which a
persistent recordset connection or an always open bound form corrects

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[dbahooker]

or of course; Access MDB is 'too chatty' and Windows 2003 just won't
put up with it's crap.

MDB is obsolete; lose the training wheels!

ADP allows you to keep most of your forms and reports.. rewriting
queries is EASY!

-Aaron