Replicated database with diff. versions of Acces?

[Guest]

Hi,

does anybody know of possible problems we might run into if we update our
client-computers from Acces 2000 to Acces 2003, with regrards to the fact
that every client has a few databases (developed under A2000) that have to be
synchronised with the server-version?

We can't update all clients at once so there will be a period in which we
have different versions of acces. This means the server-version will recieve
synchronisations from instances of the same database but from different
versions of ACCES!!

 

[Douglas J Steele]

Hopefully all your applications are split into front-ends (containing the
queries, forms, reports, macros and modules), linked to back-ends
(containing the tables and relationships). Only data (eg: the back-ends)
should be replicated: replication is not intended for application components
(the front-ends).

With that understanding, there's no reason why all your back-ends can't be
in the same version: Access 2003 will work quite happily with an Access 2000
back-end (heck, it'll work fine with an Access 95 back-end!)

 

[Joseph Meehan]

Hi,

does anybody know of possible problems we might run into if we update
our client-computers from Acces 2000 to Acces 2003, with regrards to
the fact that every client has a few databases (developed under
A2000) that have to be synchronised with the server-version?

We can't update all clients at once so there will be a period in
which we have different versions of acces. This means the
server-version will recieve synchronisations from instances of the
same database but from different versions of ACCES!!

I don't believe there is a problem, as long as, all the versions of
Access support the file format version.

 

[dbahooker]

WORK FINE?

Access MDB files don't WORK FINE without replication.

screw MDB and don't listen to these MDB wimps.
upgrade your app / db to sql server and utilize access data projects.

they are 10,000 times more powerful and reliable than silly obsolete
mdb files

 

[Tony Toews]

does anybody know of possible problems we might run into if we update our
client-computers from Acces 2000 to Acces 2003, with regrards to the fact
that every client has a few databases (developed under A2000) that have to be
synchronised with the server-version?

Your subject implies that the front ends are replicated. If so
that's not a good idea. Replication is meant only for tables and
records.

Michael Kaplan, www.trigeminal.com, has stated that replicating non
table objects is a bad idea and can lead to corruption and many
problems.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[dbahooker]

replication is only for REAL DATABASES and MDB isn't a real database.


you can sit there and tinker with bugs all you want.

but do you think that amazon.com runs on a silly mdb file?
do you think that Microsoft product activation works on a silly mdb
file?

MDB is obsolete as are all you geezers that still use it.