[AccessD] RE: AllowBreakIntoCode", dbBoolean, False

Next part of this saga...

I set the form I want to update as the startup form & everything works just
fine. When I use the switchboard as the startup form, the new form does not
work.

So, now the question is, Why is my switchboard interfering with this new
form & not allowing me to add new records?

Va.

-----Original Message-----
From: Hollis,Virginia 
Sent: Wednesday, October 29, 2003 11:51 AM
To: 'Access Developers discussion and problem solving'
Subject: 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