Ghost Aen fields from replication now causing problems

[Guest]

Hi all,

I have a DB in Access 2003 of interview data for a conservation
organisation, which i replicated to allow users in different countries to
keep entering data. I unwisely replicated the entire unsplit DB and had some
real problems with corruption so subsequently unreplicated it (using a tool
found through these fora) and split it into a front and back end for
replication.

As a result of this replication and unreplication, i ended up with a few
strange fields starting with Aen... in every table where i had a memo field.
I couldn't delete them even when i'd got rid of replication. They didn't seem
to cause a problem so i just carried on ignoring these fields. Now they seem
to be causing some problems though...

So now in my Interviewees table i have this artifact alled
'Aen_OtherIndComments'.
Today i added a field called 'BlastFishingFreq' which didn't show up in the
table design or datasheet view and it was not available to queries or forms.
I tried to add the field again but was told "cannot define field more than
once" so it obviously was there somewhere. Later, on adding another field,
the 'BlastFishingFreq' field reappeared and another field disappeared. It's
almost as if the 'Aen_OtherIndComments' field is in some way obscuring
another field.

I have no idea what is going on and have a collegue in Tanzania waiting to
use the DB. Please can anyone answer:

1. Is there anyway to delete these 'Aen_...' fields??
2. Is there any explanation and solution to Access apparently 'hiding' some
of my fields from me??

Hope that someone can help,

Thanks,

Tim

(e-mail address removed)

 

[Guest]

PS. The strange coming and going of fields happens when i try to synchronise
the database with a replica back end to pass on the new fields to the replica.

 

[David W. Fenton]

ThereAreSomeThatCallMeTim

1. Is there anyway to delete these 'Aen_...' fields??
2. Is there any explanation and solution to Access apparently
'hiding' some of my fields from me??

You need to completely recreate the replica.

Start a fresh MDB.

Use MakeTable queries to create the tables, omitting the replication
fields.

Change the properties of the fields that were not properly set by
the MakeTable to be correct (i.e., adding indexes, validation rules,
etc).

Once you've done that, *now* replicate your file.

Also, you might want to check Michael Kaplan's website,
http://www.trigeminal.com, as he has some unreplication tools that
are better than the ones provided by Microsoft.