[AccessD] RE: AllowBreakIntoCode", dbBoolean, False

That is weird.  Can you put a MsgBox Me.AllowAdditions in the OnOpen event
of the form to see if it is getting set to False for some unknown reason?
And, if so, although it's going around the problem instead of solving it
could you put Me.AllowAdditions= True in the OnOpen event of the form?

Rocky

----- Original Message ----- 
From: "Hollis,Virginia" <HollisVJ at pgdp.usec.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Wednesday, October 29, 2003 9:51 AM
Subject: [AccessD] RE: AllowBreakIntoCode", dbBoolean, False


> Ok I take that back, it isn't the AllowBreakIntoCode", dbBoolean, False, I
> changed it to True again & the form didn't allow me to add a record. If I
> run the StartUp I can't add any records, if I bypass the startup, I can
add
> records. This is crazy.
>
> Va.
>
> -----Original Message-----
> From: Hollis,Virginia
> Sent: Wednesday, October 29, 2003 11:46 AM
> To: 'Access Developers discussion and problem solving'
> Subject: AllowBreakIntoCode", dbBoolean, False
>
>
> This has me so baffled!
>
> I developed a new form in a development database. When I imported it to
the
> production database, it does not work correctly. I have a button to add
new
> records. This button does not work in the production dB.
>
> I went through everything to figure it out & narrowed (I think) it down to
> the StartUp Properties  where the AllowBreakIntoCode", dbBoolean, False
is,
> when I changed this to True, the button on form to add new records works.
>
> Why is this happening? What can I do to correct it? I use the same type of
> code on other forms to add new records & it works fine. Am I missing
> something else?
>
> Virginia
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>