I'm having a problem getting procedures stored in D3 to execute from ASP. The procedure executes in immediate mode, but not under program control. TCL commends execute fine. I suspect this is a configuration problem, but I don't have a clue as to what or where.

D3 is running under Redhat 9 and ASP.NET is on Win2K using ODBC. Has anyone run into a problem like this?

thanks,

paul

deermouse wrote:
I might be missing something but I think a lot more information than
this is necessary to diagnose a problem. Since you're running what
seems to be a current D3 release you should contact RD Support or try
posting to the RD connectivity forum where RD people and others can
comment on this. I seem to recall someone else in the forum saying
they had an issue with that and ASP.NET. ASP.NET is not ASP and the
problem might be different depending on the technology being used. By
specifying you're using ODBC I'd guess you're using the D3 Class
Library. I never use the D3 Class Library and consider it woefully
inadequate compared to more modern tools like mv.NET. But whatever
tools you're using you probably need to provide some code and tell how
you're trying to do this.

Sorry this isn't more helpful.
T

The problem is "data types". The D3Rulemodule, is a VARIANT TYPE. It
works with ASP an VBS. It cannot work in ASP.NET where there no are
VARIANTS.
It is similar to the D3write and ASP. It does not work in ASP because
in MUST be an INTEGER and VBS only works with variants.



You can go around the problem using a workfile, the d3write and a
trigger in the file. It's quite easy.

But i agree with Tony. If you want to use .net, you should not use the
"old" library. It is not for .net. You can use MV.net or PDP.net. They
are ACTUAL .net products.

Hope this help

joseba

Thanks for the replies. I agree about posting on Raining Data's forum. I've registered, but they haven't approved me yet.

I will look at the VARIANT data type issue and MV.net and PDP.net and see if that helps.

thanks,

paul