Major Issues - Pls Help!!!!!!!!!!

[nashat21]

hello.. we just converted to a new db last weekdn.. for the first couple of days we blew up once a day and the db compacted and repaired fine. however, today we've had an unusual number of blow-ups (by that i mean that the db is in an unrecognized format and requires repair)... it started when someone was inputting an OLE object into one of the fields and her computer froze. from then on it has been happening almost every hour. at one point, i lost one of the main tables in the db and i have gotten # on occassion. I had posted earlier and the suggestion was to set the option to lock the edited record. we are even considering splitting the db into a front- and back-end. please advise. not only has this been very disruptive to our business today it is also very frustrating

 

[Alexandre]

I would say: 1. Get rid of OLE objects in your DB. Eventually save them as files in an organized way so that later on you can link link them back to you DB if you want, by storing their path (only) in a field. 2.Once rid of OLE objects, repair and compact your DB. In serious cases of DB corruption, the JetComp utility (download from MS site) is a great asset. Extreme solutions include importing all your DB objects into a new DB, and decompile/recompile. 3.Set up that system to store links to files in your DB, no OLE objects (there is a tremendous data overhead associated to such objects that can end blowing up your DB as you experienced)

Hope this helps

 

[Pat Hartman]

You will find the db to be much more stable in general as well as being easier to change if you split it into the traditional front end with all the objects and back end with only tables. The front end can be shared on the server or downloaded to the individual PCs.

 

[Hellfire]

I would like to stick a spanner in the works as well now!!!

After succesfully creating MDE files from the BE on the server, suddenly MS Access doesn't want to allow that anymore.

It says:

Microsoft Access was unable to create an MDE database.

Why is that? Can I fix it in some way?

PLEASE HELP!

 

[Rich]

Why do you need to create an MDE

 

[nashat21]

thanks for your responses...

we are seriously considering splitting our database. however, does this mean that we will not be getting any more "unrecognized db format" errors? if we would, does it repair and compact the same way as it does now? also, how can the tables, forms and other db objects get updated?

another issue we have had is that some users access the db and grab exclusive control.. we have checked their settings and everyone is set to shared mode.. any ideas?

thanks in advance..

nashat

 

[Pat Hartman]

1. By splitting the db, you instances of "unrecognized db format" errors will surely decline or disappear entirely. The corruption is usually caused when one of the currently active users exits the db improperly. Most people know enough to not just hit the power off button, so these ungraceful exits are usually caused by network outages or software freezes.

2. You will need to compact the fe and be separately.

3. Having a split fe makes deploying enhancements easier. All you need to do is to replace the old fe with a new copy. This assumes of course that you don't let your users create their own objects in the db. If you have changed any table formats, you'll need to convert the old data and import it into the new structure.

4. If users acquire exclusive control without explicitly requesting it, it is because they are changing objects in the db. A2K and newer will not allow shared access to a db that has been modified unless some change management software such as SourceSafe is being used.