Connecting Tech Pros Worldwide Forums | Help | Site Map

Incorrect data format after replication

SimonDB
Guest
 
Posts: n/a
#1: Nov 13 '05
The replication of my database was successful and it works well. I can
modify tables and forms, except for one thing : VBA ! I can’t add code
in VBA, the error message : "incorrect data format".
I worked on the database before the replication, and all was ok. After
replication, on the master-replica I managed to add some code only one
time, just before close and re-open the database. That was the last
time I was able to make change in VBA.
Do you have any idea how I can repair my database ?

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/MS-Access-In...ict216403.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=741885

David W. Fenton
Guest
 
Posts: n/a
#2: Nov 13 '05

re: Incorrect data format after replication


SimonDB <UseLinkToEmail@dbForumz.com> wrote in
news:4_741885_6addef6a06229e20107d37ce0a5d7f7f@dbf orumz.com:
[color=blue]
> The replication of my database was successful and it works well. I
> can modify tables and forms, except for one thing : VBA ! I can’t
> add code in VBA, the error message : "incorrect data format".
> I worked on the database before the replication, and all was ok.
> After replication, on the master-replica I managed to add some
> code only one time, just before close and re-open the database.
> That was the last time I was able to make change in VBA.
> Do you have any idea how I can repair my database ?[/color]

Why would you have any code in a replicated database?

Replication is for DATA and ONLY for data.

Yes, Microsoft claims it works for forms and reports and codes,
which are, after all, stored in Jet data tables (actually, in Jet 4,
the whole thing is stored as a binary BLOB in one single record of
one of the system tables). But on a practical basis, experience has
taught us that REPLICATION DOES NOT WORK FOR FRONT END FILES.

And, of course, if you've not split your database into back end data
file and front end application (with forms, reports, queries,
modules), then you're running with the wrong setup in the first
place.

I understand how people think that replication looks like a great
way to distribute front end updates, but it's simply not, as the
result is a quick increase in corruption and eventually (and not
very long, either) complete loss of the project as a whole.

DON'T REPLICATE FRONT ENDS.

Ever.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
SimonDB
Guest
 
Posts: n/a
#3: Nov 13 '05

re: Incorrect data format after replication


"David W. Fenton" wrote:[color=blue]
> SimonDB <UseLinkToEmail@dbForumz.com> wrote in
> news:4_741885_6addef6a06229e20107d37ce0a5d7f7f@dbf orumz.com:
>[color=green]
> > The replication of my database was successful and it works[/color]
> well. I[color=green]
> > can modify tables and forms, except for one thing : VBA ! I[/color]
> can’t[color=green]
> > add code in VBA, the error message : "incorrect data[/color]
> format".[color=green]
> > I worked on the database before the replication, and all was[/color]
> ok.[color=green]
> > After replication, on the master-replica I managed to add[/color]
> some[color=green]
> > code only one time, just before close and re-open the[/color]
> database.[color=green]
> > That was the last time I was able to make change in VBA.
> > Do you have any idea how I can repair my database ?[/color]
>
> Why would you have any code in a replicated database?
>
> Replication is for DATA and ONLY for data.
>
> Yes, Microsoft claims it works for forms and reports and
> codes,
> which are, after all, stored in Jet data tables (actually, in
> Jet 4,
> the whole thing is stored as a binary BLOB in one single
> record of
> one of the system tables). But on a practical basis,
> experience has
> taught us that REPLICATION DOES NOT WORK FOR FRONT END FILES.
>
> And, of course, if you've not split your database into back
> end data
> file and front end application (with forms, reports, queries,
> modules), then you're running with the wrong setup in the
> first
> place.
>
> I understand how people think that replication looks like a
> great
> way to distribute front end updates, but it's simply not, as
> the
> result is a quick increase in corruption and eventually (and
> not
> very long, either) complete loss of the project as a whole.
>
> DON'T REPLICATE FRONT ENDS.
>
> Ever.
>
> --
> David W. Fenton
> http://www.bway.net/~dfenton
> dfenton at bway dot net
> http://www.bway.net/~dfassoc[/color]

Thank you for the answer. That was not what I hoped, but now it’s
clear.
So the idea is to split the database to have the front end and the
back end and replicate only the back end. That’s the idea ?

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/MS-Access-In...ict216403.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=752372
David W. Fenton
Guest
 
Posts: n/a
#4: Nov 13 '05

re: Incorrect data format after replication


SimonDB <UseLinkToEmail@dbForumz.com> wrote in
news:4_752372_fb650c39eb9bf104f36b65c9084241b2@dbf orumz.com:
[color=blue]
> So the idea is to split the database to have the front end and the
> back end and replicate only the back end. That's the idea ?[/color]

That's definitely the idea, and the only way that Jet replication
really works.

Since I've always split front ends/back ends since my first
multi-user app (my first app ever, in fact), it never occurred to me
to replicate anything but the data.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Closed Thread