BorlandTalk.com

Penny · Guest

Hi,

I use Delphi 7 and SQL Server via BDE.
Many time when I ' m trying to Edit a Query, the following message appears :
"Couldn't perform the edit because another user changed the record"
I' m the only person who runs the program, and I can't understand why this
happens.

Does anyone has an idea about it???

Thanks in advance.

George Christoforakis · Guest

I think that there are some problems concerning BDE and sql-server (is it
the 2000 version you are using?).
Think of upgrading into ADO or something else *but* BDE.
There is relative information at borland's community area.

George Christoforakis.

"Penny" <pennyargyrou (AT) hotmail (DOT) com> wrote

Bill Todd (TeamB) · Guest

If the query result includes a DateTime field this may be the problem.
There is a loss of precesion converting from the SQL Server DateTime
format to the BDE's DateTime format and back. This makes it appear
that the value of the DateTime field has changed.

The BDE uses Microsoft's DBLIB client library which has not been
updated since SQL Server 6.5 so there are some problems with 7.0 and
2000. The best solution is to move to ADO.

--
Bill (TeamB)
(TeamB cannot respond to questions received via email)

Penny · Guest

I think you are right, but it is impossible for us now, to change to Ado or
dbexpress,
Is there any other way to bypass this problem using BDE???

I' m wondering when exactly this problem happens?

It hasn't the same behaviour all the time.

I have many tables that have datetime field but I have no problem yet.
This table is Detail to a Master table. When I try to edit record "a" of
"A" row of Master everything is ok, but when I do the same thing with record
"b" of "B" row of Master I get
that horrible message.

I'm really comfused.

Please help...

Thanks in advance.

"Bill Todd (TeamB)" <no (AT) no (DOT) com> wrote

Kevin Frevert · Guest

Penny,

If your using RequestLive, make sure float-type fields (DateTime, floats,
etc) ProviderFlags are configured only to pfInUpdate (see Help for more
info). That way the BDE won't (or shouldn't) attempt to compare those
fields in the underlying Update's Where clause.

Good luck,
krf

"Penny" <pennyargyrou (AT) hotmail (DOT) com> wrote

Bill Todd (TeamB) · Guest

AFAIK, the ProvierFlags property only affects a TDataSetProvider.
Setting the ProviderFlags for the field objects has no effect on the
BDE.

--
Bill (TeamB)
(TeamB cannot respond to questions received via email)

Kevin Frevert · Guest

Bill,

Yep, that right (I just tried it).

IMO, if ADO isn't an option right now, Penny needs to write her (I'm
assuming Penny is female) own update scripts and/or check out...
http://community.borland.com/article/0,1410,22571,00.html

Thanks for the correction,
krf

"Bill Todd (TeamB)" <no (AT) no (DOT) com> wrote

Penny · Guest

Hello

Thanks you for the time you spend for me.
The problem is that I'm still wondering...
I don't want to believe that there is no way to bypass this problem.
This is not the right time to pass from BDE to dbexpress (I think this is
the best choice I have to make not ADO, because we started with ADO but we
had enormous problems with the installation of the program, tell me if this
has changed...), because as I said to my first post we now use MSAccess and
BDE and we did great work to pass from MSAccess to SQLServer, as we have a
very serious problem with the speed of our Application in one customer's
server. We have now finished and we have no other problem, apart from that
which makes me feel depressed.

Any idea maybe can save me...

Thanks a lot.

Penny (Kevin you guess right, I'm a girl)

"Kevin Frevert" <Work (AT) drinkingcoffee (DOT) com> wrote

Kevin Frevert · Guest

"Penny" <pennyargyrou (AT) hotmail (DOT) com> wrote