[AccessD] RE: AllowBreakIntoCode", dbBoolean, False

If it works on your machine and fails on theirs it would seem that there is
some difference in the two installations.  Can you check the version of
access, and the version of Jet and/or other DLLs that might be involved.
Service packs the same?  Just casting about at random now.

What would happen if you created a new db on their machine and imported all
the objects and compiled on their machine?  (Really long shot).

Rocky

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


> I am still having problems.
>
> Now users are getting error messages when they click on a button on the
> switchboard. "Error Executing Command" and the forms do not open.
>
> When I click on the buttons on my machine the forms open. What can I do??
>
> I imported everything into a new database, I have compiled, decompiled. I
> don't know what is left to try or what is causing these errors on some
> machines and not others?
>
> Virginia
>
> -----Original Message-----
> From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com]
> Sent: Wednesday, October 29, 2003 6:44 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [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
> >
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>