S
scott.sara.news
I am having major problems accessing some API's and I believe the
problem is a 16-bit app.
I originally had an application written in Borland Builder C++ 6
(32-bit)that loaded some API's for a specific database environment I
use. Everything worked great.
I am now trying to do the same thing in C# with the same DLL's but am
having a problem with one API call in particular. To begin using these
API's I have to start the environment by making an Init call. After
this, I can use any of the API calls I want. This Init call is what is
failing. Supposedly this call is responsible for starting up a 16-bit
EXE, which is the database environment. Could the .NET environment be
stopping this 16-bit app from being run from the DLL?
The funny thing is that if I start up my Borland app, and just let it
sit in the background, then I run my C# app, it works great! The Init
routine runs and works and all other calls work great. Obviously it is
because my Borland app has already run this 16-bit app and the C# call
doesn't have to.
Is there any way to force C# to run this 16 bit app from the DLL?
Any help would be greatly appreciated,
Scott
problem is a 16-bit app.
I originally had an application written in Borland Builder C++ 6
(32-bit)that loaded some API's for a specific database environment I
use. Everything worked great.
I am now trying to do the same thing in C# with the same DLL's but am
having a problem with one API call in particular. To begin using these
API's I have to start the environment by making an Init call. After
this, I can use any of the API calls I want. This Init call is what is
failing. Supposedly this call is responsible for starting up a 16-bit
EXE, which is the database environment. Could the .NET environment be
stopping this 16-bit app from being run from the DLL?
The funny thing is that if I start up my Borland app, and just let it
sit in the background, then I run my C# app, it works great! The Init
routine runs and works and all other calls work great. Obviously it is
because my Borland app has already run this 16-bit app and the C# call
doesn't have to.
Is there any way to force C# to run this 16 bit app from the DLL?
Any help would be greatly appreciated,
Scott