Allow Additions/Allow Deletions cause weird results

  • Thread starter Thread starter Laurel
  • Start date Start date
L

Laurel

I have a form which myteriously sometimes retrieved all the 10 expected
records, and sometimes didn't. When it didn't, it did produce one empty
row. This isn't just a visual problem, because the navigation button
control displays "1 of 1" or "1 of 10," depending on whether it is behaving
or not.

I stumbled onto the fact that changing the "additions allowed," etc. seemed
to change the behavior... perhaps combined with exiting out of the db and/or
compacting/repariing the db.

I've spent close to an hour doing nothing but modify the "additions
allowowed," "deletions allowed" and "data entry". As far as I understand
"data entry," the form is behaving as if it were set to "yes," even when it
is not.

Has anyone had this problem? Is there anything that can be done?

Note also, that this might be related to a previous posting I made entitled
"combo box looks empty." That problem has been coming and going as I've
been plaing with the 3 additions */data entry properties.

Unfortunately, it is now in a mis-behaving state, and I can't get it back to
behaving again. I'd hoped to show this as a prototype to a user
tomorrow.... Isn't always the case....
 
I fixed this by putting this line of code before a Me.Requery

Me.DataEntry = False

It's still a mystery why this was necessary, as the DataEntry property is
clearly set to false when viewed in the form properties window. And a
search of the whole database code doesn't uncover any hidden "DataEntry =
False" code. (I couldn't have put it in, as I didn't know about DataEntry
until this problem hit.)

This also fixed my problem with the invisible combo box data in posting
"combo box looks empty."

I'd love to hear from anyone who has an opinion about what's going on here.
 
I fixed this by putting this line of code before a Me.Requery

Me.DataEntry = False

It's still a mystery why this was necessary, as the DataEntry property is
clearly set to false when viewed in the form properties window. And a
search of the whole database code doesn't uncover any hidden "DataEntry =
False" code. (I couldn't have put it in, as I didn't know about DataEntry
until this problem hit.)
Click to expand...

That is really, really peculiar.

You might want to Decompile your database - there may be some obsolete
VBA code hanging around. Instructions at Tony Toews' website

http://www.granite.ab.ca/access/corruptmdbs.htm
 
Thanks! This web site looks like an absolute gold mine. I had been told
that you couldn't de-compile/re-compile a 2000 db the way you could 97 (I
never had 97). But apparently there are plenty of things you can do.
 
Thanks! This web site looks like an absolute gold mine. I had been told
that you couldn't de-compile/re-compile a 2000 db the way you could 97 (I
never had 97). But apparently there are plenty of things you can do.
Click to expand...

Right about the website, Tony's a Living Access Treasure. And whoever
told you about decompile was (clearly) mistaken.
 
Back
Top