DAO360 Error

Hi, I am working in Windows XP Pro.

The error is the usual exception box asking to send error report or not. The
error report data contains:

ModName: dao360.dll
ModVer: 3.60.8618.0
Offset: 00016a06

The technical info shows:
Exception Information
Code: 0xc0000005
Flags: 0x00000000
Address: 0x00000001b75a06

System Info:
Windows NT 5.1 Build: 2600

I have used a MsgBox statement in the code to track down the actual line of
code that throws the exception. I can access the properties and methods of
the recordset without a problem. The exception is thrown when I try to access
the contents of a field.

Ron

"Ralph" wrote:

>
> "Ron" <Ron.RemoveThis@discussions.microsoft.com> wrote in message
> news:C04D6C40-87DD-4E77-9861-4E3588B40D11@microsoft.com...
> > My application access an mdb database using dao360 and works fine in the
> VB6
> > SP6 IDE. When I create a deployment package and try to run it it fails at
> the
> > first attempt to access a field value. The recordcount is correct and
> > .movefirst works, but trying to get the data throughs an error in
> dao360.dll.
> > Any help?
> >
>
> You kind of skipped a few steps here.
> 1) Your app runs in the IDE.
> 2) You compiled it and tested it within your test environment.
> 3) You created a package and deployed the app without trouble.
> 4) When you run the compiled app in its new location it failed with an
> error.
>
> What's the error?
> What's the target O/S?
>
> -ralph
>
>
>
 >> Stay informed about: DAO360 Error 

"Ron" <Ron.DeleteThis@discussions.microsoft.com> wrote in message
news:73AA6822-AC4A-4F53-8997-65F7C1CA93B2@microsoft.com...
> Hi, I am working in Windows XP Pro.
>
> The error is the usual exception box asking to send error report or not.
The
> error report data contains:
>
> ModName: dao360.dll
> ModVer: 3.60.8618.0
> Offset: 00016a06
>
> The technical info shows:
> Exception Information
> Code: 0xc0000005
> Flags: 0x00000000
> Address: 0x00000001b75a06
>
> System Info:
> Windows NT 5.1 Build: 2600
>
> I have used a MsgBox statement in the code to track down the actual line
of
> code that throws the exception. I can access the properties and methods of
> the recordset without a problem. The exception is thrown when I try to
access
> the contents of a field.
>
> Ron
>

That error is just a general "unhandled exception", or "I've fallen and
can't get up." Surely there is something else going on here.

Implement an Error Handler in the procedure and catch the exact DAO error:
http://www.vb123.com/toolshed/01_bugs/access_errors.htm
http://msdn2.microsoft.com/en-us/library/bb221208.aspx

If you don't have it download MZTools
http://www.mztools.com/v3/download.aspx

This makes it easy to implement error handlers, and to manage line numbers
[Erl()] which will help to narrow the problem down.

Show your code were you are accessing the Value.

PS: For a development environment turn-off that MS Error reporting:
http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Repo...ng-Wind

It doesn't do any good as any error reported by an 'unknown' application -
i.e. "Yours" - will be ignored by MS anyway.

-ralph
 >> Stay informed about: DAO360 Error 

Thanks for the quick reply's. I have downloaded the MZTools application and
will try to learn how to use it.

In trying to simplify my code for inclusion here, I found out what the
problem was. I had the field names defined by global constants and one of
them was "Cat No" which I had specified as "[Cat No]". This does work in the
VB6 IDE but does NOT work in stand alone. Removing the brackets solved my
problem.

Many Thanks,
Ron


"Ralph" wrote:

>
> "Ron" <Ron RemoveThis @discussions.microsoft.com> wrote in message
> news:73AA6822-AC4A-4F53-8997-65F7C1CA93B2@microsoft.com...
> > Hi, I am working in Windows XP Pro.
> >
> > The error is the usual exception box asking to send error report or not.
> The
> > error report data contains:
> >
> > ModName: dao360.dll
> > ModVer: 3.60.8618.0
> > Offset: 00016a06
> >
> > The technical info shows:
> > Exception Information
> > Code: 0xc0000005
> > Flags: 0x00000000
> > Address: 0x00000001b75a06
> >
> > System Info:
> > Windows NT 5.1 Build: 2600
> >
> > I have used a MsgBox statement in the code to track down the actual line
> of
> > code that throws the exception. I can access the properties and methods of
> > the recordset without a problem. The exception is thrown when I try to
> access
> > the contents of a field.
> >
> > Ron
> >
>
> That error is just a general "unhandled exception", or "I've fallen and
> can't get up." Surely there is something else going on here.
>
> Implement an Error Handler in the procedure and catch the exact DAO error:
> http://www.vb123.com/toolshed/01_bugs/access_errors.htm
> http://msdn2.microsoft.com/en-us/library/bb221208.aspx
>
> If you don't have it download MZTools
> http://www.mztools.com/v3/download.aspx
>
> This makes it easy to implement error handlers, and to manage line numbers
> [Erl()] which will help to narrow the problem down.
>
> Show your code were you are accessing the Value.
>
> PS: For a development environment turn-off that MS Error reporting:
> http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Repo...ng-Wind
>
> It doesn't do any good as any error reported by an 'unknown' application -
> i.e. "Yours" - will be ignored by MS anyway.
>
> -ralph
>
>
>
 >> Stay informed about: DAO360 Error 

"Ron" <Ron.DeleteThis@discussions.microsoft.com> wrote in message
news:9FDC32F9-DA7E-4B70-BEAD-F8FB7E4DA67B@microsoft.com...
> Thanks for the quick reply's. I have downloaded the MZTools application
and
> will try to learn how to use it.
>
> In trying to simplify my code for inclusion here, I found out what the
> problem was. I had the field names defined by global constants and one of
> them was "Cat No" which I had specified as "[Cat No]". This does work in
the
> VB6 IDE but does NOT work in stand alone. Removing the brackets solved my
> problem.
>
> Many Thanks,
> Ron
>

Ha. Glad you got it working.

I've been bit by that one on more that one occasion myself. I should have
realized it.

-ralph
 >> Stay informed about: DAO360 Error