Access Link Table is slow....

[Timinator]

Here is my problem:
I have an 3 or 4 programs(VB Interface/Access Backend) that all have the same EmployeeTable. When an employee changes, I have to make the update in all 4 databases. I've tried making it into a link table, but it pretty much kills my program because its so slow. The link table seems to slow the connection to the database way down. Does anyone know of a more efficent way to handle this?

Thanks.

Tim

 

[CajunCenturion]

I guess the first question, is why do you have 4 different Employee Tables in 4 different databases? Is it possible to remove the Employee table from 3 of the databases, and in your application, have two connection objects - 1 to the normal database, and the 2nd connection to the database which contains the Employee Table.

If that is not possible, I would also considering looking into the JRO (Jet Replication Object) to see how you can use its capabilities it has with respect to keeping the Employee Tables synchronized.
Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Timinator]

The reason I have 4 different Employee Tables is because it is too slow to have it linked. I tried the 2 connection thing, but the only problem is that I can't use the Employee Table in SQL statements then.

I will have to look into that JRO option.

Thanks.

Tim

 

[chrisJLocke]

I use linked tables at work, and have no speed issues compared to 'normal' tables.
What flavour of Access are you using?
Are the databases 'local' on your network? We use a linked table over a 64k IDSN line without problems.

 

[Timinator]

I am using Access 2000 over a network. Perhaps I should give it another try, maybe I did something wrong last time.

Thanks.

Tim