ComboBox Not Replicating Correctly

  • Thread starter Thread starter COTA
  • Start date Start date
C

COTA

Greetings,

I'm having trouble with a combo box not populating itself correctly on a
replicated database. The control works fine in the design master. In the
replicated database the control comes up empty. The row source is a straight
foreward SQL statement on a query returning 5 columns. What's strange is
that it used to work. I had been making a number of changes in the design
master. I had been replicating on a regular basis to ensure the changes were
taking effect. On my last replication the combo box stopped working. I tried
a number of things to "shake it free" so to speak. I changed the SQL, moved
the control, renamed the form, etc... Nothing seems to work so far. Has
anyone seen this behavior before? Any advice would be appreciated. Thanks.

PS: Stats - One design master, one replicated database, Access 2002/SP2,
W2K/SP4, All tables in this database are internal (i.e. no linked tables, no
ODBC, etc...).
 
I can't tell you what specifically is happening with your
combobox, but your replication model is probably the
culprit. I went down your route of replicating the 'whole'
database in the early days and was subject to lots of little
quirks as well as some other larger issues with damaged
replicas.

The replication experts all agree that the forms, reports,
queries, code etc... should not be replicable for the most
dependable setup. The recommendation is to split your
database to a BE/FE model with just the data tables in the
BE. Now you just replicate the BE and you distribute FE
design changes as a new FE copy to the users. This keeps the
intricacies of the replication focused on just replicating
data which is the only thing that really needs replication
once your table models are complete. Even table design
changes are a light load for replication compared to the
work it does logging and tracking every design changes you
make in the FE objects.

Regards,

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________
 
Thanks for the info. I was hoping there was a simple technique I could apply
to make all my worries go away. I understand what you're saying. Looks like
I have some work ahead of me.
 
Shouldn't be too tough really. Create a new db for the FE
and import everything from the front end except the tables.
Do not make this a replica or design master. Now you should
be able to delete them from the original design master. Do
backup everything first of course, and you should synch a
few time to make sure that everything is up to speed on
replication before you do this.

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________
 
Back
Top