Recent content by suedemick

Hi, everyone, this is suedemick, again. I'm not sure, but I might have solved the problem. I think it has something to do with the fact that the linked tables belong to a split database that can only be opened through a workgroup file. When I open the new unsplit database (the one with the...

Garry, I added your code to my exit button, set the database to compact on close, and I still got the same error message and a new db1.mdb. (Of course, it didn't work when I tried menu option Tools\Database Utilities\Compact and Repair Database, since the code had no chance to run). Thanks...

cghoga, Thanks for the idea! I contacted our network help desk and they checked my permissions: theoretically, I have full permissions on the folder in question. HOWEVER, we copied the database to my workstation, and it compacted with no problems, i.e. it compacted and replaced the original...

I am developing a small (3,000KB) Access 2000 database (not yet split, due to other issues), that resides on our network. Some of the tables are linked, the rest of the tables are populated twice a day by downloading data from our AS400. I recently had to move the database from one network...

Thanks, laakins, for the suggestion! I'll check it out. Sue

Samulayo, You're right; I'm probably being overly cautious. Thanks again! Sue

Samulayo, Using a batch file sounds like a great suggestion! One concern I have with abruptly quitting database1 is, what if the user has a table open (in one of the add/edit forms) with a record unsaved? Should I somehow, before running the batch file, loop through all the forms that are...

MichaelRed and foolio12, Thank you for your thoughts and suggestions! Yes, this is more than a single user system; we have about twenty users. In the beginning, I strongly suggested that the front end database could be split into separate pieces, each representing one of the areas of focus, but...

cmmrfrds, Thanks for the links; I'll check them out! Suedemick

ccburn, Thanks for the suggestion; I compile my code if I make any changes to the code or to the underlying form/report query, or if I've added any objects to forms or reports that have code attached. When I'm done for the day, I compact my design copy of the front end two times, then copy it...

Omega36, I am using Access 2000. Database 1 has a front end with lots forms, queries and reports (58,000 KB). Database 2 is quite small (currently 4,000 KB, but under developement). A little background as to why I'm concerned about corruption: I've read that if an Access database becomes too...

cmmfrds, Thank you for your suggestion! This is a direction I hadn't considered. Maybe it would be safer to do it this way instead of linking. (I live in terror of corrupting database 1,even though I have the daily backup to fall back on) Thanks, Sue

Omega36, Thank you, thank you for responding!!! So, you don't think I will cause myself any corruption problems by opening a second database which is linked to tables in the first database (which is still open)? I'll give this a try, and thanks again, Sue

This is suedemick: Have I offended the experts here at Tek-Tips? No one has responded to my questions in quite some time, and I'm wondering if I have been blackballed and just don't know it. I don't feel that I am a very knowledgeable Access developer(when I joined, I indicated I was a...

I was wondering if I can expect any problems if I try to open a second Access database from a first database. Database 1: split, back end on the server. Database 2: not split, located on server. Some tables are links to Database 1, other tables are populated by importing information daily from...