Access 2000 keeps crashing....

[onbliss]

My client has Access 2000 database. There are about 10-15 people using it simultaneously. It kept crashing. So, somebody split the DB into the App (forms, reports, queries...) part and the DB(tables) part.

It still keeps crashing. Is there any known issues with Access 2000 crashing?

thanks

[Ecniv]

hmm.... nope probably the db design is trying to do something and running out of memory or something.

Things you could do :
- Compact and repair the mdbs (front and back) via tools>database utils
- Compile and save any coding
- Reinstall access on all machines (full install with all options of access selected)
- Create two new mdbs, one copy all the front end things in and compile and save it. The other mdb for the tables, compact and repair
- Send me all the fields etc and I'll build you a new working one in around a month hehehhe

Vince

[swatty]

I think more than 5 users is not reasonable for an Access DB.

If you got more users you should consider another robuuster DB.

[swatty]

Before it was spilt (UI , DB) How did they work on it.

All on the same mde ??

You can copy the mde to each users machine and store the Db part on a server.
You can link your tables all to the one on the server.

Like i've mentioned , more than 5 users is a bit high for an Access DB.

Did you check the size of the app.
Access has a limit of 2G.

[Ecniv]

I'm sure upto 20 users should be fine... But developers choice lol and budget too of course


Vince

[swatty]

Originally posted by Ecniv
I'm sure upto 20 users should be fine... But developers choice lol and budget too of course


Vince

I've always heard 5 was the most,
did read over here there are apps running with 20 - 25 users so don't listen to my remark about user limits.

[goatsucker]

15 users is too much I think, but it may be possible with regular compact/repairs. Do you have the Jetcomp.exe utility which is available from microsoft. You can run this from the command line, so the job can be automated.

I don't think splitting the database in this way will help. All clients will still be accessing the data layer at the same time, so if this is the problem, splitting the database into forms etc. and tables will not work.

How is the application crashing? Are your clients .mdb files or is it a VB front end?

[andreys]

Usually systems tables get corrupted a create a problems. So you need to replace them, instead of just keep them repairing.

Do this:

1.repair database (if needed at that time)
2.create a new blank database.
3.import all objects (tables, queries, forms, ...) into the blank db.

see if it helps

[JMvVliet]

Andreys post could be so helpful, I've had the same problem a few years ago, and the database keeps crashing every time. After importing everything to a new database it keeps working.

Also, network connections that are not completely ok, could make a database crash, i.e. when updating records directly via ADO. I've had that problem also a few months ago. Setting the database to another server was helpful.

Last thing I could know: when your NTFS table on the server isn't correct anymore, then the memory usage of the database in relation to the server could be the creator of the problems.

Hope it helps you find something out.

[onbliss]

1) After the split, the Access database crashes less often.

2) Nope, they are just simple MDBs. No MDEs. What are the benefits of MDE over MDB? And, ofcourse, the DB part is on a central location and the App is installed on the Users' PC.

3) Dont know about the JetComp.EXE utility. Will check it out.

4) How is the application crashing? Not much of a clue. The Users when they try opening the MDB, are not able to do so. Looks like there might be different reasons (I just took over this project, will keep digging)

5) And, thank you others for your contribution. I will try the suggesions.


ps: This is a departmental application, that the users have circumvented around the IS department. Why they circumvented? Maybe deadline, avoid red-tapism, did not want to use the preferred contractor. And, maybe for these same reasons the Users are not going use a more suitable DB. Becos, then it might land into the IS laps.

Man...lots of non-technical complications...Life was meant to be EASY...ha ha ha

[goatsucker]

The difference between an MDE and an MDB file is that the code and form modules of an mde are locked down (the E stands for executable: ie you can only execute the file and not do anything with it). Even if your application is run from the Access run-time (Where the user is only able to run forms), a few registry hacks can turn this into the "normal" version of access, so using MDE's can give you an extra level of security.

As MDEs can still have the queries and tables changed, these are most useful for front end Access applications, which link to a backend database. I don't think using MDEs will help in this case.

If the application just cannot be opened, then I would definitely try compacting/repairing the back end databases with Jetcomp.exe.