Don't know what

[IxiRancid]

to title this thread.

This is it:
The app was made for Access 2k or highier. On some workstations there is still Office 97, Access97 has problems opening highier version MDBs, will that affect my app?
If so, what to do? Its about 50 pcs.

This too - some users work on Terminal Services. If I was to install the app on the Terminal Server, users could access it normaly, but what would happen with database if two or more had it opened at the same time?
One event uses Access queries that delete whole tables, that would affect other users wouldnt it?

 

[bri189a]

Regardless whether you use Terminal Server or the standard App Access limits the amount of simulaneous connections. As far as 97 or 2000, if the application was made to use a 2000 database in its connection string, and the software was properly installed it shouldnt matter. The software installation should have the proper libraries packaged with it; you should be able to run it on a computer that doesnt have Access installed on it at all if the installation package was made correctly. In .NET, using an Access database as a backend to a program over a network is generally a bad idea because of several reasons; security being the biggest, the way Access handles connections being a pretty big reason too; so you may want to re-think the application you are using and whether it was made for the purposes your trying to employee it for and possibly come up with another solution. Ive seen programs work with an Access connection over the network; but these were programs were they knew the simulatneously connections and network load were minimal and security risks werent important.