By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,996 Members | 896 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,996 IT Pros & Developers. It's quick & easy.

SAGE L50 and ASP.net

P: n/a
Hi people!

Quick question. I am connecting to a SAGE Line50 database via Sage SDO in
ASP.net.

I can connect to the database but have problems creating a particular
workspace...

This is the message I get...

"
The server threw an exception.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: The server
threw an exception.

Source Error:
Line 41:
Line 42: ' Create an Instance of the SalesRecord object
Line 43: oSalesRecord = oWS.CreateObject("SalesRecord")
Line 44:
Line 45: 'RecordCount

"

It highlights Line 43 as the problem "oSalesRecord =
oWS.CreateObject("SalesRecord")" - any help would be superb.

Cheers

Maverick

Nov 19 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
FOTL wrote:
Hi people!

Quick question. I am connecting to a SAGE Line50 database via Sage
SDO in ASP.net.

I can connect to the database but have problems creating a particular
workspace...

This is the message I get...

"
The server threw an exception.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: The
server threw an exception.

Source Error:
Line 41:
Line 42: ' Create an Instance of the SalesRecord object
Line 43: oSalesRecord = oWS.CreateObject("SalesRecord")
Line 44:
Line 45: 'RecordCount

"

It highlights Line 43 as the problem "oSalesRecord =
oWS.CreateObject("SalesRecord")" - any help would be superb.

Cheers

Maverick


Maybe you should try to "catch" the exception and inspect it in the debugger.
I have found that the exception message for CDO was not very helpfull,
but inner exceptions had a better message. Maybe that applies here also.

Also you can try and find a "SAGE Line50" newsgroup for problems
relating to that specific product.

Hans Kesting
Nov 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.