Article View: borland.public.cppbuilder.database.ado
Article #177Re: TADODataSet and TADOTable
From: TumurS
Date: Mon, 07 May 2007 05:59
Date: Mon, 07 May 2007 05:59
48 lines
2750 bytes
2750 bytes
I found where was the problem, but another one is raised.
My dataset has details TADOQuery object.
Disabling this query (i.e. I does not open it anyway) eliminates the
problem.
The key column receives auto-incremented values normally.
But how to establish master-details schema in this case?
"TumurS" <spam_tumurbaatar@pixel.mn> wrote in message
news:463eada1$1@newsgroups.borland.com...
>I replaced TADODataSet with TADOTable and nothing changed:
> the problem with 0 key still exists. What am I doing wrong?
>
>
> "TumurS" <spam_tumurbaatar@pixel.mn> wrote in message
> news:463ea372$1@newsgroups.borland.com...
>> In my previous project there was no problem with working TADOTable
>> object.
>> Inserting, editing, removing and etc worked well. Cursor location and
>> type
>> are client and static. Auto-increment fields values retrieved correctly
>> by engine
>> after inserting new record operation.
>> I dont' remember why I choosed TADODataSet for another project, but
>> now I encountered some problem. CommandType is cmdTable and cursor's
>> location/type are same as above. After inserting a new record it's
>> auto-increment key field
>> has 0 value. I cannot do any further operation on it because the key is
>> wrong.
>> So I added this line just after opening dataset:
>>
>> (*dataset->Properties)[OleVariant(WideString("Update Resync"))]->Value
>> = adResyncAll;
>>
>> (by the way, to refer to above constant I manually included <adodb_xp.h>.
>> is it safe?)
>>
>> Now the new record disappears from local cache just after posting. Any
>> ideas?
>> Also, if my code retrieving all records from the server (i.e. no WHERE),
>> is there
>> any difference between using table and query?
>>
>> P.S. MSSQL2K and BCB6
>>
>>
>
>
Technical Details
Message-ID:
<463ebffb@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<463ea372$1@newsgroups.borland.com> <463eada1$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10698b,8ae4fe352a0e2720 X-Google-Attributes: gid10698b,public X-Google-Language: ENGLISH,ASCII-7-bit From: "TumurS" <spam_tumurbaatar@pixel.mn> Newsgroups: borland.public.cppbuilder.database.ado References: <463ea372$1@newsgroups.borland.com> <463eada1$1@newsgroups.borland.com> Subject: Re: TADODataSet and TADOTable Date: Mon, 7 May 2007 13:59:21 +0800 Lines: 50 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 202.55.183.101 Message-ID: <463ebffb@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1178517499 202.55.183.101 (6 May 2007 22:58:19 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail