If the dataset is in edit mode, should setting a memo back to the original, by using the
oldvalue (as below), be a problem?
The error only happens with client server (not local) and if I first edit the memo, tab to
another control, tab back to the memo, and then invoke code as below.

if components[i] is TDBMemo then
  TDBMemo(components[i]).Field.VALUE := TDBMemo(components[i]).Field.OLDVALUE;

Also, if the memo is edited, the above code is invoked, then the main program form is
closed without saving, an access error occurs in either local or c/s.

Dave M
--------------------------------------
dbisam 4.22 build 6 client-server

Dave,

<< If the dataset is in edit mode, should setting a memo back to the
original, by using the oldvalue (as below), be a problem? >>

Not normally, no.

<< The error only happens with client server (not local) and if I first edit
the memo, tab to another control, tab back to the memo, and then invoke code
as below.

if components[i] is TDBMemo then
  TDBMemo(components[i]).Field.VALUE :=
TDBMemo(components[i]).Field.OLDVALUE;

Also, if the memo is edited, the above code is invoked, then the main
program form is closed without saving, an access error occurs in either
local or c/s. >>

Hmm, I tried it here with the attached project and it worked fine.  Could
you see if the project fails for you ?  It uses the DBDEMOS Biolife table
transferred to DBISAM format using the BDE Database Transfer Utility, but
you could switch it to using your table instead.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Hmm, I tried it here with the attached project and it worked fine.  Could
you see if the project fails for you...
-------------------------------------------------------------------------------------

Thanks for the ***fast*** response.

I am using bds2006.  It didn't like your project file, but it could open your main form.
Your main form is not set up so as to produce the error.

I have attached an entire project which automatically produces the errors.
It uses biolife table and "Test" database.
Just compile it and click the 10030 button for the one error, or the AV button for the other.

Hopefully, it will compile and run....

Dave

Where did that attachment go??
Well, here it is again...

Dave M

Dave,

<< Where did that attachment go??  Well, here it is again... >>

Okay, the 10030 was already fixed via this fix:

http://www.elevatesoft.com/scripts/incident.dll?action=viewaddr&release=4.23&type=f&incident=2173

The AV is now fixed and will be part of the 4.23 release going out today.
It was a snafu in the TDataSet handling of record buffers inherited from the
BDE stuff.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>The AV is now fixed and will be part of the 4.23 release going out today.
>It was a snafu in the TDataSet handling of record buffers inherited from the
>BDE stuff.

I wonder what you'll blame in ElevateDB when there's no BDE stuff left

Roy Lambert

ps don't forget - you're not allowed to reply

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:52D0E796-E878-41E3-9616-3FE3449B904F@news.elevatesoft.com...
>
> I wonder what you'll blame in ElevateDB when there's no BDE stuff left
>

It'll be because of that awful legacy DBISAM stuff.

Robert

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

The AV is now fixed....
-------------------------------------------------------------------------------

Lets see...
Error submitted at about 9:00 pm, and fix done or announced by 11:00 am next morning.
That's fast.  What can I say? Thanks.

Dave

Roy,

<< I wonder what you'll blame in ElevateDB when there's no BDE stuff left
>>

Robert is correct - that damn DBISAM.

<< ps don't forget - you're not allowed to reply >>

Well, we're not officially talking about features, so......

--
Tim Young
Elevate Software
www.elevatesoft.com