[AccessD] "Object invalid or no longer set"

Bob Heygood accesspro at gmail.com
Tue May 23 19:25:53 CDT 2017


Hello Jim,
I found the offending code.
I am a big fan of MZ tools.

What I could not understand was why it did not fail for them when using A97.
Turns out it did and they didn't explain it correctly.

Thanks for the response.

Bob

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim
Dettman
Sent: Tuesday, May 23, 2017 5:27 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] "Object invalid or no longer set"

Bob,

  Get a copy of MZ Tools (or something else), which will allow you to number
the lines in a project/module/procedure.  You can do it manually as well if
you know the procedure at least and it's not large.

 Then in your error handler, use the undocumented vba.erl call, which will
give you the line number where the error occurred.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bob
Heygood
Sent: Thursday, May 18, 2017 08:45 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] "Object invalid or no longer set"

Sorry.
Should have been more clear.
The app converted fine from A97 to A2010.
And after some adjustments/rewrites to the code, debugs and works well,
except for the error noted. Which did occur under A97.
Still trying to nail down the exact offending line. This is hard as
transactions are used. 
"DAO BeginTrans, CommitTrans, and Rollback methods of the Workspace object."



"Object invalid or no longer set"

Per MS, I checked my Jet 4.0 version and it looks like I have the latest.

Any other suggestions ?

TIA
Bob Heygood



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Rocky Smolin
Sent: Wednesday, May 17, 2017 5:57 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] "Object invalid or no longer set"

At what point do you get it?  During the save as which is converting the
format?  If so, maybe try converting to 2003 first and then to 2010? Or
maybe try importing all the objects from the mdb into an empty accdb. If it
farts during the import you'll be able to see which object is causing the
problem.

HTH


Rocky Smolin
Beach Access Software
760-683-5777
www.bchacc.com
www.e-z-mrp.com
Skype: rocky.smolin
 



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bob
Heygood
Sent: Wednesday, May 17, 2017 5:06 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] "Object invalid or no longer set"

Hello to the list,
I am getting this error when converting from A97 to A2010:

"Object invalid or no longer set"

Per MS, I checked my Jet 4.0 version and it looks like I have the latest.

Any other suggestions ?

TIA
Bob Heygood

--
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



More information about the AccessD mailing list