Hi Tim,

NULL lookup fields are showing the value of of the previously accessed record.

Customer (ID, LastName, FirstName, , , )
Order (ID, CustomerID, StatusID, , , , )
Status (ID, Description)

Set the MasterSource property of the ORDER EDBTable to create a Master-Detail relationship
with the CUSTOMER EDBTable.
Create a Lookup field STATUSDESCRIPTION for the ORDER EDBTable which looks up the STATUS
table.

When browsing the CUSTOMER table, if you access a CUSTOMER without any ORDERS then fields
ID, CustomerID, StatusID are set to NULL (as expected)  . . . But the StatusDescription
field shows the value of the previously accessed record.


--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:   61 2 4930 7336
Mobile:   0419 016 032
email:   rharding@wck.com.au

Richard,

<< NULL lookup fields are showing the value of of the previously accessed
record. >>

I'll check this out, but there's an issue with 1.02 and earlier with NULL
bookmark values, so it may be the same thing.  The bookmarks go all haywire
and show the wrong rows if any NULLs are present in the bookmark values.

--
Tim Young
Elevate Software
www.elevatesoft.com

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


I'll check this out, but there's an issue with 1.02 and earlier with NULL
bookmark values, so it may be the same thing.  The bookmarks go all haywire
and show the wrong rows if any NULLs are present in the bookmark values.


--------------

Tim,

I'm experiencing the same problem with lookup fields showing wrong values.

Just to make it clear: are you planning a fix in 1.03? And if so, do you have an ETA for it?

Best regards,

Paul B

Paul,

<< Just to make it clear: are you planning a fix in 1.03? And if so, do you
have an ETA for it? >>

Yes, of course.  If there's an issue and we are aware of it, I will either:

1) Make sure that it is fixed for the next build, if I can reproduce the
problem already (the case here)
2) Make sure that the customer sends me something to reproduce the problem,
and I will postpone the build until I can get it and reproduce the problem.

1.03 should be available this week.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

I have installed 1.03 but the problem reported previously regarding lookup fields still
remains.

This appears to be my last remaining problem in migrating from DBISAM to ElevateDB so
thank you.

--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:   61 2 4930 7336
Mobile:   0419 016 032
email:   rharding@wck.com.au

----------------------------------------------------------------------------------------------------

NULL lookup fields are showing the value of of the previously accessed record.

Customer (ID, LastName, FirstName, , , )
Order (ID, CustomerID, StatusID, , , , )
Status (ID, Description)

Set the MasterSource property of the ORDER EDBTable to create a Master-Detail relationship
with the CUSTOMER EDBTable.
Create a Lookup field STATUSDESCRIPTION for the ORDER EDBTable which looks up the STATUS
table.

When browsing the CUSTOMER table, if you access a CUSTOMER without any ORDERS then fields
ID, CustomerID, StatusID are set to NULL (as expected)  . . . But the StatusDescription
field shows the value of the previously accessed record.

Richard,

<< I have installed 1.03 but the problem reported previously regarding
lookup fields still remains. >>

I'll need a project from you in that case.  I was only able to guess
previously that the issue was with the bookmark values.

--
Tim Young
Elevate Software
www.elevatesoft.com

<< I'll need a project from you in that case.  I was only able to guess
previously that the issue was with the bookmark values.  >>

Tim,

Attached is a zip file containing:
* a zip file a Delphi 2006 project,
* a zip file of the ElevateDB database
* the SQL listing.


--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:   61 2 4930 7336
Mobile:   0419 016 032
email:   rharding@wck.com.au

Richard,

<< Attached is a zip file containing: >>

Thanks very much.  It's now fixed and the fix will be in 1.03 B2.

--
Tim Young
Elevate Software
www.elevatesoft.com