Recent content by 2bb

In the end I skipped the whole concept of a back and front end database!!! I just monitor the size of the database, asking the user to log out and compact the database, giving the user a form with all users logged on, so he can ask his collegaes to log out as well. Not the most elegant...

Data is processed in back end using "docmd.openquery", runs well, no problems, data ok. But in next step in the code, I use the data processed (calling a query or table based on the data processed) and the code tells me f.e. "3112 Record(s) cannot be read; no read permission on 'x'" or "3107...

Thanks DCrake. Actually still will have the problem to synch between two db. The amount of data is too large, I suppose, so tmp (or back end) is still processing or didn't give tables / queries free to front end, before I reach next step in code, getting al kind of DAO error messages in the...

Thanks atomic. That really is the problem. I first only had a front end, but after import to a tmp table it became to slow, so I had to compact and repair before contuining, that's why I splitted my app in a front and back end. Getting synch problems. Do you see an alternative?

Thanks Galaxiom and boblarson, I first check whether everybody logged out before compacting. Not deleting the tables is not an option. I want to be sure all data provided is imported. After import I start looking whether all colums I expected exist, if not I can give the user a message...

Dear reader, In my db I import quite a lot of data. It grow to fast, so I had to split it into a back and front end, so I could compact and repair the back end after each import, without bothering the user. Works well. However the data is processed and I use multiple statements to delete tmp...