Buy Support
Incidents |
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
Click Here
|
Buy Support
Incidents |
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
Click Here
|
|
ADO recordsets no longer like a null in the SalesOrPurchasePrice? |
Author |
Message |
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-04-02 10:52:43 |
We have verified this as an issue and am trying to figure out why ADO no longer likes a null in the SalesOrPurchasePrice. It is okay with nulls in the SalesAndPurchaseSalesPrice field.
If you change the ADO cursor type to:
Const adUseServer = 2 oRecordset.CursorLocation = adUseServer
It works just fine. We are continuing to investigate why this is an issue. And just in case you try switching everything to adUseServer, please be aware stored procedure calls like sp_tables only like adUseClient cursor types.
|
|
|
|
|