"Compact on close" and MsysDb error

[Zedbiker]

I have just updated our ordering database and after looking on this forum
thought it would be a good idea to use the "Compact on close" function.

The database is held in a central folder on the network.

After completing the update, closing and restarting the database I get the
"MsysDB" error.
Luckily I had backed up the database before I started work on it so I was
able to roll back.

Is it just a coincidence or could the "compact on close" function be
corrupting the database?

Many thanks for any advice/ thoughts.

 

[Maurice]

In contrary to what you say the people in this group will not advise you to
compact and close within a function (or set it in the db options for that
matter). Most of the problems start when this feature is set. So do the
compressing and repairing manually or schedule it when nobody is using your
mdb.

 

[Zedbiker]

Thanks Maurice

I have seen it mentioned it on various topics within this forum but whether
you could class this as advice to do it I don't know. Anyway I have removed
it as you suggested. I have also decided to split the database as advised by
many.

I would prefer to leave the front end and backe end on the server as I am
improving regularly as I learn more about Access. I have seen many say the
front end should be on individual machines. What is the down side of keeping
it in one location?

I know this is probably a seperate topic but I hope you don't mind me asking.

Many thanks again.

 

[Douglas J. Steele]

I would prefer to leave the front end and backe end on the server as I am
improving regularly as I learn more about Access. I have seen many say the
front end should be on individual machines. What is the down side of
keeping
it in one location?

Having people share a single front-end significantly increases the risk of
corruption.

Having the front-end on the server increases network traffic (since all
forms, reports and code need to be moved across the wire before they can be
executed).

Tony Toews has a free Auto FE updater avaiable at
http://www.granite.ab.ca/access/autofe.htm Using it, you put a copy of the
current front-end on the server, and the utility will automatically copy
that front-end to the user's workstation if what they have is an older
version.