strange performance Issue

[Jeremy]

Not to long ago we upgraded from Access 97 to Access 2003. I have a front
end and a backend. The front end gets compiled into a MDE file and placed
out on our servers. The backend tables reside out on the servers. Since
upgrading when I'm trying to make changes to the front end on my hard drive
it runs super slow, just changing a label can take 20-30 seconds, almost
like it is constantly pulling data off the back end. Is there setting in
access or is anyone aware of this NEW annoying feature in Access 2003?

 

[Arvin Meyer]

Not to long ago we upgraded from Access 97 to Access 2003. I have a front
end and a backend. The front end gets compiled into a MDE file and placed
out on our servers. The backend tables reside out on the servers. Since
upgrading when I'm trying to make changes to the front end on my hard drive
it runs super slow, just changing a label can take 20-30 seconds, almost
like it is constantly pulling data off the back end. Is there setting in
access or is anyone aware of this NEW annoying feature in Access 2003?

Since Access 2000, there has been a changed in the Save method in Access to
reduce corruption. Access now does a monolithic save, which means it
littlerally saves every object in the database every time you push the save
button. In a large database, especially if it's running from the server,
this can take a while.

NEVER run a front-end from the server. Although you are reducing chances of
corruption by running it compiled (as an MDE), you still are begging for
corruption by sharing the front-end file from the server. It is faster, and
safer to copy the MDE to the desktop every morning, than to run it from the
server.

You can save time during development by using a sparse front-end to make
changes then copy the forms and reports back to the main database at the end
of the day, compact it and make an MDE.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Jeremy]

Again, were not running it from the server, The only thing residing on the
server during development is the data or the mdb of tables. All development
is done on local computer. Database isn't that large the tables are only
about 1.4 mb in size with probably 1000 entries in the main table.

 

[Paul Overway]

Check Tools|Options...turn off Name Autocorrect (if you haven't done so).

 

[Tony Toews]

Not to long ago we upgraded from Access 97 to Access 2003. I have a front
end and a backend. The front end gets compiled into a MDE file and placed
out on our servers. The backend tables reside out on the servers. Since
upgrading when I'm trying to make changes to the front end on my hard drive
it runs super slow, just changing a label can take 20-30 seconds, almost
like it is constantly pulling data off the back end.

You need to keep a connection open to the backend at all times. Such
as a bound form or a recordset. This is also required for the
users but also for any developers.

For more information on this and other performance problems, 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