Re: Corrupt form...or so it seems

From: Tracy (tracy_at_nacservices.com)
Date: 07/23/04 

Date: 22 Jul 2004 22:36:49 -0700

Hi Reggie,

Thanks for taking the time to help me with my problem (people helping
people, it's a beautiful thing...).

Your suggestions for possible sources of the problem are great places
to look, but don't apply in this case (see below). I truly think this
form is corrupt and the source of my problem. I've never had an app
with a corruption problem like this so I'm in uncharted territory and
looking for a little guidance on corruption-recovery. I'm going to
start from a new db and pull in everything except this one form, and
re-design that from scratch. Any suggestions for how else to
"corrupt-proof" my app would be great appreciated.

Specifically let me address your questions:

<The first is you stated that the form is based on a query. Is it
possible that the query that the form is based on uses the values you
are changing as criteria? In other words is the data still in the
table, but no longer meets the criteria to be displayed on the form.>

Sorry if I wasn't clear in my original post, but the recordsource for
the form that I think is corrupt is the Customers Table (not a query).
 And the record *really* is gone (not just missing from a query
result).

The form that IS based on a query is the form that appears on startup,
which draws information from, among other things, the Customers Table.
 This is where I'm getting the "invalid argument" error after the
customers table has been corrupted. This form isn't meaningful to my
problem, it just happens to be where the first error message appears
after re-starting the application after the Customers table has blown
up.

<do you have relationships built that would cascade updating/deleting
etc. joined records in other fields.>

There's no cascade delete issue - the record is disappearing from the
Customer table, the same table the (corrupt?) form is based on.

>open the code window. Select Tools/Options and select the General
Tab. Make sure break on unhandled errors is selected.>

Already set to break (an error message could very well be popping up
when it "craps out" as my user put it, but these boys have actual
*work* to do and documenting my error messages are WAY down their list
of their priorities!).

At this point, simply re-designing the form from scratch seems the
fastest way to get this app up and running reliably. I just hope
that's ENOUGH to get it up and running reliably!

I really appreciate you taking the time!
Tracy