Why does it keep changing back?

  • Thread starter Thread starter ZigZagZak
  • Start date Start date
Z

ZigZagZak

Hello-
Getting kinda frustrated with a form......
I have a main form & a subform. The subform I want to be an entry
form...but when I put it to "data entry" in the properties, it keeps changing
back to not a data entry form..........


WHY???? haha its making me crazy!

thanks!
 
Hello-
Getting kinda frustrated with a form......
I have a main form & a subform. The subform I want to be an entry
form...but when I put it to "data entry" in the properties, it keeps changing
back to not a data entry form..........


WHY???? haha its making me crazy!

thanks!
Click to expand...

Access version? Have you Compacted and Repaired? What is it doing that
convinces you it's not Data Entry? Are you aware that Data Entry means "don't
show me any old data, just let me add new records, but show those new records
until I close the form"?
 
ZigZagZak said:
Hello-
Getting kinda frustrated with a form......
I have a main form & a subform. The subform I want to be an entry
form...but when I put it to "data entry" in the properties, it keeps
changing
back to not a data entry form..........


WHY???? haha its making me crazy!

thanks!
Click to expand...


Exactly how are you changing it? Are you opening the subform separately in
design view, changing the Data Entry property manually, and saving it?
 
VER 2003, I don't think I have compacted/repaired this database. What makes
me think that is because the forms properties keep switching from yes to no.
And I don't know why. And ya, I know what a data entry form does, I have
made several data bases with them in general, just not one that had it as a
subform. I might be doing something stupid, so it keeps reseting defaults or
something......Not sure
 
VER 2003, I don't think I have compacted/repaired this database. What makes
me think that is because the forms properties keep switching from yes to no.
And I don't know why.
Click to expand...

Open the database, and select Tools... Options... General. UNCHECK "Track Name
Autocorrect Info" if it's checked - this misfeature has richly earned the
nickname "Name Autocorrupt". Compact and repair, and try again. This shouldn't
be happening but you're not alone...
 
Hi,

If your main form is not data entry, then it may be forcing all
subforms into non-data entry. Maybe?

Clifford Bass
 
Clifford Bass said:
Hi,

If your main form is not data entry, then it may be forcing all
subforms into non-data entry. Maybe?
Click to expand...


It's a good idea, but it didn't work that way in my tests.
 
Linq Adams via AccessMonster.com said:
I've never actually seen Access change the property in the property box,
but
the AllowEdits, AllowAdditions, AllowDeletes and Data Entry properties of
a
form used as a subform are over-ridden by how these properties are set in
the
Main form. If Data Entry is set to No on the Main form, in effect it'll be
set to No for the subform, because the subform is an object of the Main
form.
Click to expand...


Can you give me a repro scenario? As I said, I tested a form with subform,
with the main form's Data Entry property set to No and the subform's Data
Entry property set to Yes, and it worked exactly as I expected: main form
normal, subform in data entry mode. I tested with Access 2003.

Now, if it were the other way around -- main form Data Entry, subform not --
it would certainly look at first sight like the main form was overriding the
subform, because every record on the main form would be a new record, so the
related records in the subform would have to be new ones. But a little
experimentation shows that the subform is not really in data entry mode.
The same thing holds true for the other properties I listed.
Click to expand...

It is true that if the main form's AllowEdits property is set to No, then
the records on the subform can't be edited either. But that's not true for
AllowAdditions or AllowDeletions. Test it yourself, and tell me if you get
different results than I do.
 
Are you trying to do this via code?

I had a similar problem a while back, where I had a subform in continuous
mode (AllowAdditions = False), and what I wanted to do was put the subform
into data entry mode when the user clicked an "Add" button.

What I found was that IAW Access Help, "The DataEntry property has an effect
only when the AllowAdditions property is set to Yes"

--
HTH
Dale

email address is invalid
Please reply to newsgroup only.
 
Holy cow guys!....To answer one of the questions, yes I was changing it in
design view through the properties box, yes I had "allow addditions" marked
as yes as well. I will try some of the things that were suggested though,
thanks for all the replies!!!
 
If your still having issues after trying all those above you might look at
how you have your record locking setup, since it appears your main form is
using the same table as your subform it is possible that Access is preventing
the subform from being a data entry form due to record locking.

Also if you are using a query for the subform (you should always use queries
and not tables directly as thats more versatle for making changes without
"redesigning"), and your underlying query is not an "editable" query (i.e.
you can edit or add data) then the form (or subform in this case)
atomatically becomes uneditable.

Just another couple thoughts of what to look at..
 
Back
Top