Converted Database is replicating itself

[Guest]

Hi All,

We generated an Access 97 database some years ago, and we handle very
important information with it.. We are in the process of updating it to
Access 2000, but when we thought it was ready, as soon as the users started
accessing it, it would generate sequential copies (db1, db2, etc...) of
itself.

This database was updated in a computer that had only Access 2000, but the
users have both Access 97 and Access 2000 in the same computer.

Could the replication be caused by having both versions in the same
computer, is there any other option I should look at? How can I fix this?

Thanks in advance and kind regards

 

[Guest]

Hi, Marte.

Is this an unsplit, shared database located on a networked server? Is the
"Compact on close" option set? If so, the database is attempting to compact
the database when someone exits the application, but can't because others
still have the database open. Split the database into a front end (queries,
forms, modules, et cetera) and a back end (tables and relationships only).
Place the back end on the networked server, and place a copy of the front end
on each user's workstation. Users should not be sharing the front end -- or
a single database file on the network, either.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.

 

[Guest]

Hi Gunny,

You're right, it's a single database shared in a network folder with the
Compact on Close option on. We will work in splitting the application, so
thank you for your answer, and specially for being so fast.

Kind regards.

 

[John Vinson]

Hi All,

We generated an Access 97 database some years ago, and we handle very
important information with it.. We are in the process of updating it to
Access 2000, but when we thought it was ready, as soon as the users started
accessing it, it would generate sequential copies (db1, db2, etc...) of
itself.

This database was updated in a computer that had only Access 2000, but the
users have both Access 97 and Access 2000 in the same computer.

Could the replication be caused by having both versions in the same
computer, is there any other option I should look at? How can I fix this?

Thanks in advance and kind regards

The most likely reason is that the database has been set to Compact on
Close; and that the users don't have Delete permission on the folder
containing the database. The compaction process works by creating a
new database named db1 (or db2 if there is a db1, etc.), copying
everything into it, and renaming the db1 and deleting the old
database.

Check the users' permissions on the database folder: they need full
create, edit, delete permission.

John W. Vinson[MVP]

 

['69 Camaro]

You're welcome. Once you split the database, you might be interested in
automating the distribution of any new front ends with Tony Toews's (MVP)
AutoFE utililty. With this utility, the developer places the new front end
on the server and the next time the users open the application, the new
front end is saved to their hard drives and they start using it. Please see
the following Web page for more information on his utility:

http://www.granite.ab.ca/access/autofe.htm

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

 

[dbahooker]

hey once you update to access 2000 you really should migrate to an
ACCESS DATA PROJECT.

i mean-- you say your data is important


MDB is dead; it is a pain in the ass

and tony is a sqlwimp

you can easily keep all your data and queries in once place (how's that
for a backend.. shit these mdb script-kiddies just drive me crazy)

i mean

SPLITTING MDB INTO FRONTEND AND BACKEND MAKES IT HARDER TO WORK WITH;
WITH ALMOST NO BENEFIT.

KEEP YOUR IMPORTANT DATA IN MSDE OR SQL SERVER: USE ACCESS DATA
PROJECTS TO KEEP YOUR EXISTING INVESTMENT IN MDB FORMS AND REPORTS.

dont listen to these guys; shit

'you can use my code to update your frontends and backends '

GAG ME WITH A ****ING SPOON KIDS