A
Adam Z
Sorry about the incorrect system date on my last message.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
Dirk Goldgar
Adam Z said:Sorry about the incorrect system date on my last message.
Check out Tony Toews' Access Performance FAQ page:
http://www.granite.ab.ca/access/performancefaq.htm
There are lots of good tips there, some of which can make a *huge*
difference.
T
Tom Ross
How did you link the tables to the front end. I found that when I linked my
tables via the network neighborhood (\\server\database\db.mdb) response was
slow. I got better response by setting a mapped network drive on each users
machine and linking via that drive (s:\db.mdb ).
tables via the network neighborhood (\\server\database\db.mdb) response was
slow. I got better response by setting a mapped network drive on each users
machine and linking via that drive (s:\db.mdb ).
D
dabeck
Set your computer date to the actual date and wait your turn
A
Adam Z
Hi all,
I was wondering if someone could give me insight into the following problem.
Working in Access 2000 in Windows 2000.
I am making a new version of an Access database for making invoices. I
made one big fancy form, with several different subforms that I display on a
tab control. This was working very well until I split the database, and now
it goes as slow as molasses.
I have tried a couple of things -- indexing a bunch of different fields,
reducing the number of sub-forms, moving the "client" side of the database
from the network to a local hard drive--but nothing really works. In fact,
this form even goes slow in design mode!
The split I did was nothing fancy -- just moved the tables from the original
MDB (on a networked drive) to a new MDB on the same networked drive and
linked to them (eventually I want to be able to link to the tables in the
old version of the database) . The table are all regular Access tables.
The only complication I can see is that I converted the "server" MDB to
Access 97 because 1 or 2 users are still using Access 97.
Does anyone have any suggestions? It really would be convenient to have the
tables separate from the application; it would allow me to switch quickly
between test data and production data, it would let me role out the new
application to some users, while allowing others to continue to update the
tables with the old application, it would eliminate the need to do data
conversions, etc.
But if I can't get it to work, I will have to go back to having the tables
in the same MDB with the forms / queries and reports, with all the
inconveniences this implies. Any suggestions or insights would be
appreciated.
Happy holidays to all,
Adam
I was wondering if someone could give me insight into the following problem.
Working in Access 2000 in Windows 2000.
I am making a new version of an Access database for making invoices. I
made one big fancy form, with several different subforms that I display on a
tab control. This was working very well until I split the database, and now
it goes as slow as molasses.
I have tried a couple of things -- indexing a bunch of different fields,
reducing the number of sub-forms, moving the "client" side of the database
from the network to a local hard drive--but nothing really works. In fact,
this form even goes slow in design mode!
The split I did was nothing fancy -- just moved the tables from the original
MDB (on a networked drive) to a new MDB on the same networked drive and
linked to them (eventually I want to be able to link to the tables in the
old version of the database) . The table are all regular Access tables.
The only complication I can see is that I converted the "server" MDB to
Access 97 because 1 or 2 users are still using Access 97.
Does anyone have any suggestions? It really would be convenient to have the
tables separate from the application; it would allow me to switch quickly
between test data and production data, it would let me role out the new
application to some users, while allowing others to continue to update the
tables with the old application, it would eliminate the need to do data
conversions, etc.
But if I can't get it to work, I will have to go back to having the tables
in the same MDB with the forms / queries and reports, with all the
inconveniences this implies. Any suggestions or insights would be
appreciated.
Happy holidays to all,
Adam
J