F
Fuad
Hello ,
Could you please help me with the issue I faced a few days before while
installing my database into the server. I do it quite frequently when get the
version upgraded in the following sequence: install database, run User-Level
Security Wizard to set the users' parameters/create shortcut and close the
database. I have the repair/compress event running when the database closes
and saving it finally in approx 30 MBytes size. Usually, everything goes
well, but during last session the database saved itself as 50 MBytes and
created a new copy database named "db1" as 30 MBytes. Next attempt in
opening/closing database resulted in creation of the second copy "db2" with
the same 30 MBytes size. I resolved this issue by just deleting bigger file
and renaming the smaller copy with bigger's name instead of automatically
assigned "db" type name. After 3-4 attempts the database stopped creating the
copies and work well now.
Could anybody explain me this Access behavior, actually I'd rather fix it
than perform all these operations every installation session.
Thanks.
Could you please help me with the issue I faced a few days before while
installing my database into the server. I do it quite frequently when get the
version upgraded in the following sequence: install database, run User-Level
Security Wizard to set the users' parameters/create shortcut and close the
database. I have the repair/compress event running when the database closes
and saving it finally in approx 30 MBytes size. Usually, everything goes
well, but during last session the database saved itself as 50 MBytes and
created a new copy database named "db1" as 30 MBytes. Next attempt in
opening/closing database resulted in creation of the second copy "db2" with
the same 30 MBytes size. I resolved this issue by just deleting bigger file
and renaming the smaller copy with bigger's name instead of automatically
assigned "db" type name. After 3-4 attempts the database stopped creating the
copies and work well now.
Could anybody explain me this Access behavior, actually I'd rather fix it
than perform all these operations every installation session.
Thanks.