Specific problem with xp runtime and Windows 98 workstations

[Karen Hart]

My Access XP application runs perfectly on over 100 XP and Win2K
workstations, but on Windows 98 I am having a problem. I believe I am on
the latest patch of Access runtime, too, since I run
Art2002Sp3-kb834693-client-enu.exe at the workstation, after installing the
application created with the XP developer Wizard.



My application is basic. It is a front end that runs at the workstation,
accessing the back end data that resides on the server. There are no
libraries or add-ins.



The problem comes when I run a macro that does the following:

Action: Transfer Database

Transfer type: export

Database Type: Paradox 5.x

Database name: c:\mergefiles

Object Type: Query

Source: Q_ExportDataToWP

Destination: mergedata.db



Upon executing this macro, Microsoft access crashes. The details of the
"send error report" reads:

AppName: MS access.exe

AppVer: 10.0.6501.0

ModName: mspbde40 one of the.dll

ModVer: 4.0.2927.2 offset 0000b.df1



If I manually run the query, it runs fine, with the appropriate results.
But the macro, which is virtually just running the macro as it exports it to
a paradox file, blows up. I don't think it's the export to Paradox feature,
since I have similar queries attached to similar macros that work fine.



Again, the application works perfectly on XP or Windows 2000 workstations.



Before getting into the details of this simple, select query, does anyone
have any ideas as to what might be going on?



Many thanks,
Karen

 

[Karen Hart]

Yikes, is anyone out there??

My Access XP application runs perfectly on over 100 XP and Win2K
workstations, but on Windows 98 I am having a problem. I believe I am on
the latest patch of Access runtime, too, since I run
Art2002Sp3-kb834693-client-enu.exe at the workstation, after installing
the application created with the XP developer Wizard.

My application is basic. It is a front end that runs at the workstation,
accessing the back end data that resides on the server. There are no
libraries or add-ins.

The problem comes when I run a macro that does the following:

Action: Transfer Database

Upon executing this macro, Microsoft access crashes. The details of the
"send error report" reads:
AppName: MS access.exe
AppVer: 10.0.6501.0
ModName: mspbde40 one of the.dll
ModVer: 4.0.2927.2 offset 0000b.df1

If I manually run the query, it runs fine, with the appropriate results.
But the macro, which is virtually just running the macro as it exports it
to a paradox file, blows up. I don't think it's the export to Paradox
feature, since I have similar queries attached to similar macros that work
fine.

Again, the application works perfectly on XP or Windows 2000 workstations.
Before getting into the details of this simple, select query, does anyone
have any ideas as to what might be going on?

Many thanks,
Karen

 

[Chris Mills]

Yikes, is anyone out there??No. Probably no-one knows.

If it were me, which fortunately it's not, I would try and re-register the dll

Regsvr32.exe mspbde40.dll

The reason is highly technical - I wouldn't know what else to try!
(this will prove the file exists and is registered on your errant PC)

The above also doesn't make sense because you said you can export manually. If
you have similar queries in similar macros which work fine, and this query or
macro works fine on other PC's, then gosh I don't know what's the difference?
Are you exporting different data? Maybe there is some corruption in one of the
specific table records you are exporting? How you find that, I don't know
except by a process of elimination.

HTH
Chris

 

[Chris Mills]

Because I'm not out here and don't use that file, this is just another wild
guess.

Another thing worth checking might be the version.
On my Win98 machine I see:
mspbde40.dll 4.00.4331.6 in the Windows\System folder.

I see:
mspbde40.dll 4.00.2927.2 in other folders which I specifically generated under
Access2000.

Since I have upgraded this machine from A2k to A2k2, umm, anyways that does
not sound like the version for A2k2 SP2.

How are you distributing XP runtime? (since MS never provided a method to
integrate SP updates into your CD, only a customer installing updates after
installation)
see:
http://groups-beta.google.com/group...me+SP-2+with+your+app&rnum=3#0a6973967fb9afbc
(sorry, can only find my instructions in history)
Chris