slow performance accessing remote DB

[stench]

Hello everyone, I'm experiencing extremely slow database access when accessing it through a Win98 share on another machine.

I'm using Visual Basic 6 and an Access Database which runs fine when the database is on the local machine, but slows to a crawl when accessing it through a share from another machine. The database isn't that big and the second computer is on the same network, so I don't think the queries should take that long.

I've experienced this on several different machines on separate networks, so it's not a network or PC problem.

Is what I'm trying to do a good idea? Is there something else I should be doing to speed it up.

Any replies or suggestions are much appreciated...

Chris.

 

[dilettante]

Hard to know what you mean by "slow." Do you have a database design problem (in the area of keys and searching on items that aren't keys) that makes Access suck the whole file over the wire over and over again doing searches and updates?

Applications like this really should not be using Access anyway. You need a client/server database. Even MSDE would make a big difference in the amount of stuff you shove back and forth over the wire.

 

[dilettante]

See

http://msdn.microsoft.com/library/techart/acaccessprojects.htm

to get started.

Also see

http://msdn.microsoft.com/library/techart/apg01.htm

and

http://msdn.microsoft.com/library/periodic/period99/rd1099.htm

There is a lot of info out there. People really do need to start looking at taking off the training wheels, you sure aren't the only one. Of course "Access" (actually Jet, which supports .mdb files) certainly does have its place, but not in cases where you have lots of users and activity.

But in your case maybe you really have a database design problem. Look at your SELECTs and your keys. Maybe you're just missing a primary key somewhere or something.

This might give good enough local performance, but when you run it over the wire it would bog down.