Microsoft OLE DB Help

I hope i can explain this properly! We use an application (GMS) written (i think) in C. The application uses a MS Access database to store data/records etc. The GMS is an off-the-shelf product and we cannot perform a number of crucial operations we need to achieve with the data. So, to get over this problem, we have created out own app (SDM) that extracts the data from the MS Access databases and puts it into a MYSQL database so that we can work the data as we need to. As it is mainly web based, SDM is is written in PHP and uses Microsoft.Jet.OLEDB.4.0 to connect to MS Access and pull the data from the database. The problem is that reading directly from the MS Access database that is used by GMS causes GMS to crash due to some form of 'exclusive lock' error that GMS needs on the MS Access table. Up until now, we have got over this by first taking a copy of the database and then working from the copy. This is done every 15 seconds. we have now reached the stage of development of our own app (SDM) where working with a copy of the Access table is no longer acceptable. We need to be able to read/write DIRECTLY into the Access database that GMS uses. Previous attempts at this have resulted in crashing out GMS because of this 'exclusive lock' issue already described. So, i would like to know if anyone out there can use the Microsoft.Jet.OLEDB.4.0 protocol to its fullest and get it to read/write from the live database without crashing out the GMS application. I hope i have made sense! Please ask for clarification. ## Deliverables 1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the worker's Worker Legal Agreement). 2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. ## Platform C, [login to view URL], PHP