🚀 go-pugleaf

Thanks for your reply Vassiliev.

Vassiliev V.V. wrote:
> #include <comobj.hpp>
> 
> namespace System
> {
>  void __fastcall CheckSafecallResult(HRESULT hr)
>  {
>   OleCheck(hr);
>  }
> }
> 

Firstly, I don't really understand what this code is all about but I'm 
assuming I should place it at the top of the unit in question.  It seems 
to compile alright, however ...

> ...
>  ADODataSet1->Properties->Item["Update Criteria"]->Value = adCriteriaKey;
> 

this line did not.  It generated the following compile errors.

E2034 Cannot convert 'char *' to OleVariant'
E2342 Type mismatch in parameter 'Index' (wanted 'const OleVarient', got 
'char *')
E2451 Undefined symbol 'adCriteriaKey'

I used the following:

ADODataSet1->Properties->Item[WideString("Update Criteria")]->Value = 
adCriteriaKey;

which got rid of the first two errors but the last is still a mystery.

I found that "adCriteriaKey" was defined in a number of header files 
including adoint.h, however by including this file I got dumped with all 
sorts of problems including multiple declarations and scope ambiguity 
errors.

Any further enlightenment on this would again be much appreciated.


Regards,

Ian.





> ----------------------------------------------------------------
> Regards,
> Viatcheslav V. Vassiliev
> http://www.oledbdirect.com
> The fastest way to access MS SQL Server, MS Jet (MS Access)
> and Interbase (LCPI provider, http://ibp.lcpi.lipetsk.ru) databases.
> 
> "Ian Hood" <ian@ravar.net> �������/�������� � �������� ���������:
> news:3e2cb1ca@newsgroups.borland.com...
> 
>>Hello all.
>>
>>I am having an ADO problem in the guise of frequent EOleExceptions with
>>message 'Row
>>cannot be located for updating. Some values may have been changed since it
>>was last read'.
>>
>>I've narrowed the problem to the fact that the default for AdoExpress
>>datasets is to locate the record to update on all field values
>>(adCriteriaUpdCols). So if you change a row in
>>one dataset all the field values no longer match when you try to update it
>>from the second dataset. That is why I keep getting the fail messages.
> 
> I've
> 
>>also seen the problem even
>>if there is only one dataset open!!
>>
>>To solve this problem, I have to set the 'Update Criteria' dynamic
> 
> property
> 
>>to adCriteriaKey, which tells the dataset to use only the Primary Key to
>>locate the record.
>>
>>In Delpi, this is done as follows:
>>
>>ADODataSet1.Properties['Update Criteria'].value :=adCriteriaKey;
>>
>>My problem is working out how to implement the above line in C++.
>>
>>Any help in this matter will be much appreciated.
>>
>>Ian.
>>
>>
> 
> 
>