does access need split tables - getting lock ups & errors 1

[jgaweda]

i am running access on a local server drive. All new replacement to 14 QAWIN databases. i need multiple users access to forms(tables) at the same time on different records. I am getting intermittent lockups and cant exit the program, out of memory - admin in use - errors from users. am i perhaps using too many resources and need to split the databases. all pcs are 300 mz min w/ 32 ram, some 64. all the db's are on a shared server drive as .MDB. could the setup need tweeking?

 

[DougP]

Make your Database an .MDE <br>
It's a complied version of your .MDB<br>
You still need Access to run it.<br>
<br>
click tools, Database utilities, Make MDE<br>
All of your users will need to run the .MDE <br>
I had similar probelms mulitple users, corruption etc.<br>
<br>
Rename the .MDB to something different<br>
Like Mydb.mdb to -Mydb.mdb<br>
Otherwise you will have some users in the .MDB and others using the .MDE<br>
The .MDE and .MDB are to separte databases and will have different records and updates in the tables.<br>
<br>
This will also let you know right away if you forgot to tell or change a users icon.<br>
Cause it won't be able to find the .MDB <br>
<br>
also when you make a change to a form or report you have to remake the .MDE<br>
hope this Helps<br>

 

[jgaweda]

if i understand u correctly the .mde is a condensed version of the .mdb. if i move the entire directory off the lan rename the files & resetup defaults for users will all new records only go into the .mde? the .mdb can be reused every time i want to make cghanges only like a blank shell?

 

[DougP]

Yes you make changes to the .MDB only, then you must re-compile it to make a .MDE.<br>
Click tools, Database utilities, Make MDE<br>
The user's use the .MDE only.<br>
And to make sure they are using only the .MDE rename the .MDB Like I said I just put a dash &quot;-&quot; in front of it<br>
like -WIP.MDB the users use WIP.MDE.<br>
If you forgot to change someone they will let you know because they cannot open the .MDB its changed.<br>
Also I make Icons for them on their desktop.<br>
to do this click this icon and bingo they are right where they need to be. Then they won't stumble around and accidentally open the dash .MDB or rename it.<br>
<br>
I started doing this (making .MDE's) about 9 months ago and all of my, I mean ALL of my database problems went away.<br>
<br>
See when several people are using the database the likely hood of someone crashing is much greater.<br>
If they happened to have an Access database opened it might get corrupted. Usually the VBA code is what gets trashed. <br>
So if that code is in form or sub form It won't load you will get one of 3 or 4 error's.<br>
All of my Database's have at least a few lines of VB code.<br>
So corruption happened daily several times a day on 20 or more .MDB's<br>
Also if you can't open a form or report all is not lost<br>
you can still get import the tables and queries in a new .MDB.<br>
<br>
And this goes without saying BACKUP daily.<br>

 

[jgaweda]

i tried it and it worked like a charm. For me to have split the tables and do it for every user would have been a pain in the ass. i followed a few threads and i noticed people who did that using novell and win 98 still had problems (my server setup).I notice that the import export records still works. Have u had any .MDE corrupt? I also have a few lines of VBA Code. I've been using QA & QAWIN for a few years and was very low maintenance, and this product appears to be designed ass backwards. Just about every default from font to print options isnt what you want and has to be adjusted. <br>
Anyway thanks a million.