compact database conflict

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hi sir/mdm,

i have a huge db where i set it to auto compact when it close to avoid it
corrupt due to the db size is very huge. If i do not compact it when it close
it encounter corruption problem few times. it works fine if only one user
using the db, it will compact the db to the original db name.

but when i do the above i encounter another problem when i share the db to
few users in the company it will have problem when multiple users using it at
the same time where when one user quit the program and close the db it
compact the db to default temp db name as db1. so end up when all users quit
will have different db name in the shared drive and every db is not covered
changes made by all users, in other words no centralized db.

so any suggestion on how to overcome this problem?

rgds
Mei Yoong
 
Mei,

Compacting a shared db on close does not work, as you have already found
out. In that case you need to resort to a different approach, such as
running a scheduled job every night to compact your database.

Important: a shared database should always be split to a front end /
back end, with the back end sitting on the server, while every user has
their own local copy of the front end. The price paid for not doing that
is corruption! Even on a split database, frequent compaction of the back
end is a very good idea.

HTH,
Nikos
 
Hi Nikos,

thanks for your advice. beside that i also encounter another problem when i
run my report as can't open too many databases. i already tried to open and
closed every recordset in my modules. so any other way to avoid the problem?

rgds
Mei Yoong
 
Mei,

If you are certain that you are closing all recordsets and setting to
Nothing the recordsets as well as the CurrentDb objects you are
creating, if you are using DAO, then I don't know what else to suggest.
If you don't get an answer in this thread by tomorrow then you should
probably start a new one with the appropriate subject.

Nikos
 
hi Niko,

Thanks 4 ur advice.

Nikos Yannacopoulos said:
Mei,

If you are certain that you are closing all recordsets and setting to
Nothing the recordsets as well as the CurrentDb objects you are
creating, if you are using DAO, then I don't know what else to suggest.
If you don't get an answer in this thread by tomorrow then you should
probably start a new one with the appropriate subject.

Nikos
Click to expand...
 
Back
Top