Re: 127 Column Limit

Tech-Archive recommends: Fix windows errors by optimizing your registry

"Bill" <b@xxxxx> wrote in
news:#u9ZjT9oHHA.3264@xxxxxxxxxxxxxxxxxxxx:

I inherited a small Access database that uses replication to
support a mobile application. While I'm not new to MS-Access, I am
new to its replication functionality.

1. Am I imagining a 127 column limit to tables in a replicated
database? One of the first changes I had to make to the database
was to add columns to a fairly wide table. All but one of the new
columns are visible in Access.

Do you have SHOW HIDDEN OBJECTS turned on? If not, you won't see the
replication fields.

That is, 127 columns are visible and the 128th isn't. But I know
the column was added successfully since I can see it (along with
all the replication-related columns) if I import the table to a
non-replicated database (and also Access won't let me add the
column again in the replication master).

There is something wrong with your data schema if you think you need
127 columns. I've never had any tables beyond about 50 colums, and
even those could have been better normalized.

The limit on the number of fields in a replicated table is going to
depend on what kind of fields you have. Replication adds at least 3
fields, but for every memo field, it adds at least one more field.
If you have a lot of memo fields, you are likely to encounter
corruption problems and should probably split those out into a
separate memo table.

But 127 fields is without question a poorly normalized structure and
should be rethought from the ground up.

2. How does one make a copy of the replication master for
development/testing? I've already found out I can't assume a
non-replicated database works the same as the replicated ones. And
I'm certainly not going to develop in the production system. What
does one do?

Use a replica for your development and when you have to make schema
changes, make your replica the design master. Then when you roll out
your schema changes, you'll have to redo them in the real design
master.

Keep in mind that you should only be replicating data tables -- you
shouldn't be replicating the front end at all. You should have your
app split into back end (data tables only) and front end
(forms/queries/reports/etc.) with links to the back end. And the
front end should not be replicated because replication simply does
not work for front ends.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Re: Remove Replication ID?
    ... the database to a non-replicated database. ... I can use replication ID as foreign key. ...
    (microsoft.public.access.replication)
  • Re: UNKNOWN REASON (-1017)
    ... Are you running scheduled synchs in the ... > There is one memo field in the app, which I will convert to text, ... >>> indirect replication and they purchased all new equipment. ... > server pc and he also has updated software then the only common ...
    (microsoft.public.access.replication)
  • Re: Replication as a Performance Enhancer?
    ... View/Edit mode, and Data Entry mode. ... The first form captures initially reported information in textboxes ... investigation in textboxes and a memo field. ... would Access 'replication' be a ...
    (comp.databases.ms-access)
  • Re: Sync Failed; Record is Deleted -- Append Confusion
    ... is that some rescued records may have outdated data when compared ... fix the problem that's breaking replication, ... you need to figure out what caused the corruption. ... with a replica in which a user is currently editing a memo field. ...
    (microsoft.public.access.replication)
  • Re: Sync Failed; Record is Deleted -- Append Confusion
    ... fix the problem that's breaking replication, ... you need to figure out what caused the corruption. ... with a replica in which a user is currently editing a memo field. ... unbound textbox (load the data into the unbound textbox in the ...
    (microsoft.public.access.replication)