Multi User Replication...

[Arvin Meyer [MVP]]

That's very interesting. What version of Access was it created with?
Were you using the same version to unreplicate it? Was it perhaps
corrupted in some way?

I'm not sure, but I believe it was created in 2002, and that's the version I
tried running the code with. The format was the default Access 2000 format.
I don't believe it was in any way corrupted. In any case, I imported
everything into a new file after the first failed attempt, and it did the
same thing. After manually un-replicating it, it was just fine.

 

[Goobz]

You need *three* files:

- A Backend .mdb file stored on the server, containing *ONLY* the tables.
- A Frontend .mdb file, kept in a safe place, thoroughly backed up; this will
contain all the Forms, Reports, Queries, macros, modules, etc. with links to
the backend. Any design changes to forms and the like will be made in this
database.

- The .mde frontend:
Once you have the frontend .mdb file working, compile it (open the VBA editor
and select Debug... Compile); compact it; and finally create a .mde file. This
is a pseudo-compiled version of the frontend (which will NOT let you modify
any code or forms or reports, hence the need to keep the .mdb); you would
distribute copies of it to each user.

             John W. Vinson [MVP]

Okay... So here is what I am doing, and please tell me if there is
some step that I am missing somewhere, that I just don't know about,
or if I just need to keep a copy of all 3 of these files, in a folder
hidden on the server somewhere.

1: Working off my original "S:\Telecom\Phones.mdb", and am running the
TSI Unreplicator on it to "C:\Database\Phones Database.mdb".
When opening this file, it only contains the Tables and Forms. I
manually just copied my Queries into it from the replicated database.

2: Form "DN Update" has been set in the startup options.

3: Using the new mdb file, I compact, decompile, then recompile my
database. It is now copied to "S:\MISOPS\ADMIN\TELECOM\Phones
Database.mdb"

4: At this point, I have a clean, non-replicated copy of my database.
It is snuggled away nicely where someone would have to look for it,
but we all have rights to it.

5: After removing an existing Linked Table, I ran the "Database
Splitter", which successfully completed. After it was done, I relinked
the prior linked table.

6: I once again, compacted, de/recompiled, and recompacted all files.

7: I now have "Phones Database.mdb", "Phones Database_be.mdb", and
"Phones Database.mde" files.

8: I ran the "Make MDE/MDA" file, and now have a "S:\TELECOM\Phones
Database.mde" file, which when ran, has tables, queries, and forms on
everyones copy.

So what you are saying, is I need to keep all 3 of these files, and
make my form changes, table changes, etc., on the main "Phones
Database.mdb" file, and then they will appear on the .MDE file?

 

[John W. Vinson]

<8 steps snipped>

Perfect. Right on the money.

So what you are saying, is I need to keep all 3 of these files, and
make my form changes, table changes, etc., on the main "Phones
Database.mdb" file, and then they will appear on the .MDE file?

Not quite. You will need to again use Tools... Convert... Make MDE once you've
made changes to the .mdb file, and overwrite everyone's old mde file with the
new one.

Tony Toews' front-end updater will automate this for you, or you can use
google groups to search for many other examples of how this can be done.

John W. Vinson [MVP]

 

[Goobz]

<8 steps snipped>

Perfect. Right on the money.


Not quite. You will need to again use Tools... Convert... Make MDE once you've
made changes to the .mdb file, and overwrite everyone's old mde file with the
new one.

Tony Toews' front-end updater will automate this for you, or you can use
google groups to search for many other examples of how this can be done.

             John W. Vinson [MVP]

I appreciate the information and confirmation that I did it
correctly! Now, is it deemed neccessary to go into each file and do
a "File>Backup Database", or is it sufficient to backup just the BE
database file?

 

[Douglas J. Steele]

The BE definitely should be backed up.

Since each user's copy of the FE should be the same, there's no need to
backup each one.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

<8 steps snipped>

Perfect. Right on the money.


Not quite. You will need to again use Tools... Convert... Make MDE once
you've
made changes to the .mdb file, and overwrite everyone's old mde file with
the
new one.

Tony Toews' front-end updater will automate this for you, or you can use
google groups to search for many other examples of how this can be done.

John W. Vinson [MVP]

I appreciate the information and confirmation that I did it
correctly! Now, is it deemed neccessary to go into each file and do
a "File>Backup Database", or is it sufficient to backup just the BE
database file?

 

[John W. Vinson]

I appreciate the information and confirmation that I did it
correctly! Now, is it deemed neccessary to go into each file and do
a "File>Backup Database", or is it sufficient to backup just the BE
database file?

Back up the backend, *very thoroughly and carefully*; check the backup every
time you create one to be sure it's valid and working. I'd keep at least two
or three generations just in case a problem is discovered later.

Back up the .mdb frontend equally carefully.

The .mde files can be recreated from the .mdb whenever they're needed so no
backup is required.

John W. Vinson [MVP]