Archived from groups: microsoft.public.windowsxp.general (More info?)
I recently upgraded from 2000 Pro to XP Pro - SP2. When debugging VB6
programs, I am getting an error code 53 - file not found. The file is an
in-house written DLL. Prior to going to XP, I was able to call this DLL. I
can read other DLLs in the same directory with no problem. I've viewed the
DLL with Dependecy Walker and it looks OK. Another PC in our office that is
running XP Pro - SP2 does not have the same problem. Any suggestions?
> I recently upgraded from 2000 Pro to XP Pro - SP2. When debugging VB6
> programs, I am getting an error code 53 - file not found. The file is an
> in-house written DLL. Prior to going to XP, I was able to call this DLL. I
> can read other DLLs in the same directory with no problem. I've viewed the
> DLL with Dependecy Walker and it looks OK. Another PC in our office that is
> running XP Pro - SP2 does not have the same problem. Any suggestions?
Archived from groups: microsoft.public.windowsxp.general (More info?)
Sorry, that's not it. The DLL has not been moved nor changed. It ran OK
before I went to XP - I get a file not found after I upgraded.
"Byte" wrote:
> Error 53 - File Not Found. May occur when attempting to run custom reports
> http://www.prd-software.com.au/prd [...] .asp?id=41 > --
> Some days you're the windshield,
> some days you're the bug.
>
>
> "mbaugh70" wrote:
>
> > I recently upgraded from 2000 Pro to XP Pro - SP2. When debugging VB6
> > programs, I am getting an error code 53 - file not found. The file is an
> > in-house written DLL. Prior to going to XP, I was able to call this DLL. I
> > can read other DLLs in the same directory with no problem. I've viewed the
> > DLL with Dependecy Walker and it looks OK. Another PC in our office that is
> > running XP Pro - SP2 does not have the same problem. Any suggestions?
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.