Re: Corrupt form...or so it seems

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Ernie (AccessNewbie_at_discussions.microsoft.com)
Date: 07/23/04 

Date: Thu, 22 Jul 2004 17:10:32 -0700

The only time that I've gotten an "Invalid Arguement"
error was when my db exceeded the 2Gb limit. Compacting
the db takes it back down below 2Gb and so the error goes
away. You might want to check on the size of your backend
(no pun intended).

If it is too big, move some of your tables to a second
backend and link them back into the original.

>-----Original Message-----
>Tracy, 2 things come to mind from your description. 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. Another thing, do you have
relationships built that
>would cascade updating/deleting etc. joined records in
other fields. 2
>other things to check/set to make sure the error message
pops up. Open the
>db in design view. Select Tools/Startup from the main
menu. Click the
>Advanced button and make sure Use Access Special Keys is
selected. Now
>press Alt:F11 to open the code window. Select
Tools/Options and select the
>General Tab. Make sure break on unhandled errors is
selected.
>
>--
>Reggie
>
>----------
>"Tracy" <tracy@nacservices.com> wrote in message
>news:d688441a.0407221004.1f29a243@posting.google.com...
>> Hello All,
>>
>> First of all, let me thank you for all for the hours of
work this
>> newsgroup has saved me! But now I've got a problem I
can't find a
>> posting for so I need your help.
>>
>> I've got a form that's corrupting my database...or so I
think.
>> Sometimes it works fine, but three times now when the
user goes to
>> edit the data in one of the text boxes the underlying
record is
>> spontaneously deleted and the table (the customer
table...naw that's
>> not important) is corrupted. Repairing the backend has
done the trick
>> so far, but my client understandably wants a stable
program (imagine
>> that).
>>
>> The record deletion is happening when they add to or
change text in a
>> text field for an existing record (and it's not a
problem with the
>> text box since it's happened on two different text
boxes). My point is
>> that it's NOT happening upon saving the record, or even
moving to
>> another control. There's no code anywhere in the form
to delete the
>> record, and Allow Deletions is set to NO. I don't get
a corruption
>> error when I open the form, and sometimes it does work
fine, but that
>> sure sounds like a corrupt form to me. For the record,
they tell me at
>> the moment it happens that it just "freezes up"...I
can't get a
>> specific error message out of them, if there is one.
By the time I
>> get there, upon opening up the app it gives me
an "invalid argument"
>> error when it tries to open the default form, which is
based on a
>> query which pulls from the now corrupt customer table.
Does that
>> sound like a corrupt form to you?
>>
>> So here's my plan. I'm going to starts with a new db.
Pull in all
>> the stuff, *except this friggin' form*, from my
existing database and
>> rebuild my customer form from scratch.
>>
>> The problem has only happened on this one form, but is
that enough
>> information to say that the form, indeed, is the source
of the
>> problem? Or could the problem lie in the underlying
table?
>>
>> So should I also build a new backend, or at least a new
customer
>> table?
>>
>> Any suggestions would be much appreciated.
>>
>> Thanks!
>> Tracy
>
>
>.
>

Quantcast