jet or msde ???

[reshmaravindran]

Hi,

I have an application that use Access as the backend. Everything works fine when I run it on a single machine.. but if there is a lot of processing on the same database on a network the database get's corrupt and cannot be repaired. I have not done anything to handle concurrency except for using ADO.
The problem is what should be done to avoid database corruption. Would using the MSDE engine help ?

thanks,
Reshma

[antares686]

Access was never truely designed to be a network application. Small workgroup with on a segment would work fine but still not the best thing to do.

MSDE is nothing more the SQL Server Lite so yes it would offer you all the bennifits of having a real SQL Server without the major cost.

[DeivaGanesh]

Go for MSDE- but remember about its drawback it can serve a max of 5 or 10 Concurrent connections.

[M Owen]

A means of handling concurrency in Access on a network is to not have all work done on the main tables. Each user gets a "temporary" table (like a scratchpad) and processing is done from the temporary to the "live" tables ... That really is the only way ...