Populating dataset crashes app without error message

[minima producciones]

Hello,

The scenario is this: VB.net 2003 connecting to Access 2003 using Jet
4.0 SP8 and MDAC 2.7 SP1.

On a particular client machine with XP SP2, while trying to fill a
dataset it crashes fantastically without ANY error message. the exe
just disappears from the task manager.

I use a Module to launch the MainApp form, if I try to connect within
the Module BEFORE calling the:

dim MainApp as new MainApp
application.run(MainApp)

....the datasets work normally, but if I do it inside the Form_Load (or
anywhere inside the form) it presents the previously mentioned fatal
crash.

I have updated the clients machine with the SP1 for .NET 1.1 with no
luck.

Now, in a desperate attempt, I have installed VB.NET 03 in the client
machine and with the dev env it works fine, but if I try to run the
executable from outside, it crashes again. No error message from the
exception handling inside the app, no unhandled errors from the
framework or the OS, it just vanishes from the task manager.

I tried to reinstall MDAC and Jet but the installers find the previous
files and won't update with the new ones. Tried also reinstalling .NET
framework and the error persists.

Help!

 

[Jeroen Mostert]

The scenario is this: VB.net 2003 connecting to Access 2003 using Jet
4.0 SP8 and MDAC 2.7 SP1.

On a particular client machine with XP SP2, while trying to fill a
dataset it crashes fantastically without ANY error message. the exe
just disappears from the task manager.

Is there anything in the event log? If the runtime itself crashes, it
typically logs this.

I use a Module to launch the MainApp form, if I try to connect within
the Module BEFORE calling the:

dim MainApp as new MainApp
application.run(MainApp)

...the datasets work normally, but if I do it inside the Form_Load (or
anywhere inside the form) it presents the previously mentioned fatal
crash.

This could be a lot of things, not the least of which would be COM apartment
state problems. See, for example,
http://msdn.microsoft.com/library/system.threading.apartmentstate(VS.71).
But it might be another COM problem altogether; debugging those is not fun.

I have updated the clients machine with the SP1 for .NET 1.1 with no
luck.

Now, in a desperate attempt, I have installed VB.NET 03 in the client
machine and with the dev env it works fine, but if I try to run the
executable from outside, it crashes again. No error message from the
exception handling inside the app, no unhandled errors from the
framework or the OS, it just vanishes from the task manager.

You could try running it under AppVerifier
(http://technet.microsoft.com/library/bb457063) and/or one of the native
debuggers (http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx)
and see if there's anything useful in there.