[AccessD] Strange Table Behavior...

Thanks Susan and John C for your feedback.

I tried Susan's suggestion to update the table using *SD* as the criteria
and replace it with SD, but, alas, no luck there.  I even deleted all the
SD's from the table, then reloaded them (using a query of course...), but no
luck there either.  Well, I guess I had "luck", just bad luck...

So this time I repeated what I did last week to get rid of it: using a
make-table query, I created a whole new table from this one.  Set the tables
up the same (key fields, etc...), broke the relationships to the old one,
deleted it, renamed the 'new' one to the original, rebuilt the
relationships, and ... voila...it didn't work either.  FINE.

So, being a CobbleMeister, I put code in the FE to check for the SD search
and automatically make it SD*.  It works, but I don't like it.  I personally
hate making the code try to match data quirks.  However, I now do NOT have
the county Recorder buggin' me about it.

There still has to be an explanation as to why this occurs occasionally, but
I can't spend a bunch of time trying to figure it out...particularly if I
have a work-around that makes the client happy.  The client may be happy but
the programmer is bug-eyed trying to figure it out.

And on top of everything, I found out yesterday they (the County people) are
serious about converting this app, from Access 97, to Access 2003 with SQL.

This 'fun' may never end...

Greg


----- Original Message ----- 
From: "Susan Harkins" <ssharkins at bellsouth.net>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Tuesday, January 20, 2004 1:34 PM
Subject: Re: [AccessD] Strange Table Behavior...


This is really over simplistic, but have you tried just deleting SD in the
lookup table and re-entering it? You might also run an update on your many
table -- *SD* = "SD"

I've seen phantom characters work their way in before. The only way to get
rid of them is to just delete them and re-enter the data. You're lucky,
since you know the field it's in and even if it's in the many data, an
update query should take care of it. If it's a phantom character, you won't
find it. On the other hand, do any of your operators/users have access to
action queries? Almost sounds like someone accidentially changed the SD
string in your many table.

Have you tried entering a dummy SD record to see if the old method can find
it? Just curious. How are you entering that "SD" string? Might check there
too.

Susan H.