Best replication

Best replication

Post by Konra » Wed, 17 Sep 2003 15:30:22


Hi

I'am writing replication in my application
using JRO. First I created replika master
from main database on server. Next additional replica
was created and copied to another machine.
On this two databases was made changes and
the second database (additional repl.) was
once more copied to server via ftp and synchronized
with master. After this, some messages about errors
are displayed using sec. replica but databases
looks to be identical. Using replica master
dont gives error messages and works fine.
What can be wrong in this scenario and reason of
error messages. Error message is:

The expression On Open you entered as the event property setting produced
the following error:

*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
*There may have been an erro evaluation the function, event, or macro.

Thanks
Konrad
 
 
 

Best replication

Post by Konra » Thu, 18 Sep 2003 02:07:06

Thank you very much for answer.
I didn't find this info in articles before.
Pls point me some example of
replication (maybe JRO) which
meet this conditions.
Do I create partial replica?

Thanks
Konrad


"Michael (michka) Kaplan [MS]" < XXXX@XXXXX.COM > wrote in

instability,


produced

 
 
 

Best replication

Post by Konra » Thu, 18 Sep 2003 03:43:47

I'am using database which have extension
mde and comes from Access2000.

"Michael (michka) Kaplan [MS]" < XXXX@XXXXX.COM > wrote in

instability,


produced
 
 
 

Best replication

Post by Konra » Thu, 18 Sep 2003 08:24:50

I have found:

Once a database is saved as an MDE file, it can be replicated; however,
replication is only recommended in situations where no further changes need
to be made to the original database. There is no way to make changes to the
design of forms, reports, or code in the Design Master MDE file, and design
changes made in the original database can't be synchronized with
pre-existing MDE replicas. For this reason, if you need to make a design
change to a replica set of MDE files, you must make that change in the
original database, re-save it as an MDE file, and then create and distribute
an entirely new replica set from the new MDE file.

http://www.yqcomputer.com/





"Michael (michka) Kaplan [MS]" < XXXX@XXXXX.COM > wrote in

instability,


produced
 
 
 

Best replication

Post by Jack MacDo » Thu, 18 Sep 2003 13:04:17

eplication is intended for the backend part of a split Access
application. The backend contains just tables, the frontend contains
forms, queries, reports, etc. MDE files are only for frontend -- they
would serve no useful purpose on a backend.

Therefore, mixing replication and MDE's is just a bad match. It may be
possible to do it... just not wise.

Frontends are better distributed using other tools such as Tony Toews
frontend application. You can find a link in my signature.




On Wed, 17 Sep 2003 01:24:50 +0200, "Konrad"
< XXXX@XXXXX.COM > wrote:



=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd
 
 
 

Best replication

Post by Konra » Thu, 18 Sep 2003 15:09:53

s I read about this tool it copies only
mde from server to client. In case my customer
changes are made simultanously on client and server
mde but not in the same tables. Do this tool assure
proper exchanging of info?

Thanks
Konrad

"Jack MacDonald" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
need
the
design
distribute
ml/acconAboutSavingReplicatedDatabaseAsMDEFile.asp
instabiliy).
macro.


 
 
 

Best replication

Post by mich » Mon, 22 Sep 2003 21:48:43

"Konrad" < XXXX@XXXXX.COM > wrote...

Konrad,

The fact is that your original error is caused by replicating a db with
"Access project" objects in it. If you are interested in seeing the problem
resolved, you will need to look into alternatives. The suggestion given:

1) Split the database (solves the instability issue)
2) Replicate the backend with the tables (solves your update issue)
3) Use an alternate method to get people the frontend updates

Tony's solution is a way to do #3 an allow for automatic updates to the
frontend, but note that it is probably not needed if you have an MDE since
you were unable to update the frontend objects anyway.


--
MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.