Hollis,Virginia
HollisVJ at pgdp.usec.com
Thu Oct 30 16:18:36 CST 2003
Something strange has happened to the SQL Server connection. Now keep in mind - this has been working for months now with no problems, this week something has changed and I have no clue what happened. Somehow the connection has been changed. First change I found, the data was coming from the development server instead of production. I looked at the tables and there were all these records with test test as the title. Now it is requiring a password to SQL Server. I have the ODBC connection to the SQL Server tables. I relinked the tables, set up a new connection and it is still not working. Of course IT tells me they have not changed anything, but they are working on the problem. Very frustrating! -----Original Message----- From: John Colby [mailto:jcolby at colbyconsulting.com] Sent: Thursday, October 30, 2003 12:05 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] RE: AllowBreakIntoCode", dbBoolean, False Delete the links and relink to the tables. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Hollis,Virginia Sent: Thursday, October 30, 2003 12:41 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] RE: AllowBreakIntoCode", dbBoolean, False I think I Finally figured it out. Some forms would open for the users & others would not. Then it finally hit me a while ago. The forms they cannot open are ones that are linked to SQL Server tables - ODBC. I was sure it was because I added the new form & tables. I am not sure how to fix it or why it happened. But I sure feel a lot better. Virginia -----Original Message----- From: Charlotte Foust [mailto:cfoust at infostatsystems.com] Sent: Thursday, October 30, 2003 10:51 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] RE: AllowBreakIntoCode", dbBoolean, False Make sure the same version of MDAC is installed on all the machines. Differences in that can cause really weird behavior in Access. Charlotte Foust -----Original Message----- From: Hollis,Virginia [mailto:HollisVJ at pgdp.usec.com] Sent: Thursday, October 30, 2003 7:18 AM To: 'Access Developers discussion and problem solving' 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 _______________________________________________ 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