Has anyone gone through process of converting your own assembly language routines to dll (required for conversion from AREV to OpenInsight)?

Anne,

Which assembly routines in particular? It will depend on their functionality as to whether you create a new DLL or merely use an existing Win32 API call.

The Sprezzatura Group

World Leaders in all things RevSoft

Yes, I have.

My advice is to bite the bullet and recode it in C. The main reason for this is because you are going to have to convert it from 16-bit assembly to 32-bit assembly anyway.

Pat

They are our own ASSEMBLY routines.

I have converted several from assembly to C++. Using Microsoft Visual Studio 6.00. I can call the functions from my 32-bit C++ programs, but when trying to use them from OpenInsight I get the following error:

ENG0805 TEST, line 7. Function fnTest2dll does not exist in dynamic link library TEST2DLL.

Here is my TEST procedue:

Compile Function Test(a,b)

Declare Function fnTestdll

Declare Function fnTest2dll

Declare Function GetSystemMetrics

Declare Subroutine RowSel

i=GetSystemMetrics(22)

val=fnTest2dll()

RowSel("",252,253,"","",0,"","")

output=a:" plus ":b

Return output

Here is my Prototype Record DLL_TEST2DLL:

TEST2DLL

INT STDCALL fnTest2dll(VOID)

Anne,

Here is my Prototype Record DLL_TEST2DLL: TEST2DLL INT STDCALL fnTest2dll(VOID)

What is the actual name of your DLL file? If it is TEST2.DLL then I believe your prototype record should have TEST2 (or TEST2.DLL) instead of TEST2DLL in the first line.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

The name is TEST2DLL.DLL.

But I think that I know what the problem may be. For some reason the DLL has the "decorated names" exported, so OI is not recognizing them.

I need to rewrite the DLL's so that it exports the "simple name"

View this thread on the forum...