Ian


>    No offence but at this stage I think I will bundle it up and send it to Tim for assessment.

Many have tried, but I don't follow modern practice and its almost impossible to offend me

Roy

VBG

Ian,

<< If I clicked the Last button in the Navigator, all but one of the bins dissappeared. ?????  Nothing would restore them except restarting the test app. >>

This indicates that the target table is probably corrupt.  Did you verify the table to make sure that you don't have index issues ?  Also, please see my reply on the other thread regarding Windows 2012 and higher with direct, local sessions sharing databases, as it may be playing a part, also.

Tim Young
Elevate Software
www.elevatesoft.com

Ian,

Okay, I finally got a chance to look at your project.  The issue is that you have the Parts table set up as the target of a lookup field *and* bound to a TDataSource/TDBGrid control.  Doing that will cause the TDataSource and lookup field to fight over the current record position, and will give you the weird results that you're seeing.  Just make sure to use a *separate* dataset for each purpose, and that will fix the issue.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Ian,
>
> Okay, I finally got a chance to look at your project.  The issue is that you have the Parts table set up as the
> target of a lookup field and bound to a TDataSource/TDBGrid control.  Doing that will cause the TDataSource and
> lookup field to fight over the current record position, and will give you the weird results that you're seeing.  Just
> make sure to use a separate dataset for each purpose, and that will fix the issue.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com

Hi Tim,
   Doh!  So obvious when you point it out.  One for th ememory banks on what not to do.
   Thanks for the assist.
Regards,
Ian