jack.dingler
April 15th, 2005, 12:09 PM
I'm writing an extended stored procedure for SQL 2000.
The versioning worked for VS 6.0 but I'm having problems with 2003.
My function set up is:
extern "C" ULONG DAFMAPIEXT_API __GetXpVersion()
{
return ODS_VERSION;
}
When I run the DLL, I get an error:
2005-04-15 23:05:48.89 spid51 Using 'DAFMAPIExt.dll' version 'UNKNOWN' to execute extended stored procedure 'xp_DAFExchSQL_StartSession'.
Yet the following function is found by the server just fine.
extern "C" SRVRETCODE DAFMAPIEXT_API xp_DAFExchSQL_CreatePSTFile(SRV_PROC* pSrvProc);
Is SQL Server expecting a different calling convention for __GetXpVersion() than it is for extended stored procedure calls?
Jack Dingler
The versioning worked for VS 6.0 but I'm having problems with 2003.
My function set up is:
extern "C" ULONG DAFMAPIEXT_API __GetXpVersion()
{
return ODS_VERSION;
}
When I run the DLL, I get an error:
2005-04-15 23:05:48.89 spid51 Using 'DAFMAPIExt.dll' version 'UNKNOWN' to execute extended stored procedure 'xp_DAFExchSQL_StartSession'.
Yet the following function is found by the server just fine.
extern "C" SRVRETCODE DAFMAPIEXT_API xp_DAFExchSQL_CreatePSTFile(SRV_PROC* pSrvProc);
Is SQL Server expecting a different calling convention for __GetXpVersion() than it is for extended stored procedure calls?
Jack Dingler