P
Paul Hammond
I have a Access database on a network that gets used by 15 or twenty users.
It doesn't get a lot of traffic, but they tend to log on Tuesday morning, so
it can get relatively busy. All tables are stored in a back end database.
The main problem with the db is it is very slow for some users and others
can't even log on sometimes. The closer they are to the server, the
quicker it runs. For some it is excruciatingly slow. I have done some
experimenting putting the tables in SQL Server and the response time improved
dramatically.
Long story short. What are the pitfalls of doing this? Will I have to
manually add the SQL Server to each user's data sources?
Hate to jump from the frying pan to the fire.
Paul Hammond
Richmond, VA
It doesn't get a lot of traffic, but they tend to log on Tuesday morning, so
it can get relatively busy. All tables are stored in a back end database.
The main problem with the db is it is very slow for some users and others
can't even log on sometimes. The closer they are to the server, the
quicker it runs. For some it is excruciatingly slow. I have done some
experimenting putting the tables in SQL Server and the response time improved
dramatically.
Long story short. What are the pitfalls of doing this? Will I have to
manually add the SQL Server to each user's data sources?
Hate to jump from the frying pan to the fire.
Paul Hammond
Richmond, VA