I am not sure whether this is a Raize issue, or one of the ElevateDB
database engine. It feels like a Raize issue, but ... the problem does not
occur when using the BDE. So, I will post in two Newsgroups.

The tRzDBComboxBox is a Raize version of the tDBComboxBox, with the extra
feature that besides a given set of 'Items' they have a 'Values' property,
which (if defined) is a set of strings that are stored in the database
instead of the corresponding 'item'. So, you can show items 'Amex' or
'Visa', but store values 'A' or 'V' respectively

We have an tRzDBComboBox that offers its field six Value/Item combinations
(all with value <> item). All records have a non-null value that is in the
Values list.

(1) when the app starts up on record 1 of the table involved, the combo is
blank.

(2) when you scroll to subsequent records, the control shows 'values'
(should be 'items') as long as all visited records have the first possible
value.

(3) It switches to showing 'items' (which is correct) as soon as you hit a
record with a value that is not the very first possibility.

When using a tRzDBComboBox without defining 'Values', we still get an empty
control when starting on record 1. (So, we may have two separate problems
here.)

All working fine when we use the BDE. Now where is the issue?

RJ

Just found a workaround: change the field to a non-first value (and back) in
the Create of the Form that holds the combos.

RJ

"Royke" <royke@canada.com> wrote in message
news:DE076D7F-D88C-478A-89EA-846ADBED3216@news.elevatesoft.com...
>I am not sure whether this is a Raize issue, or one of the ElevateDB
>database engine. It feels like a Raize issue, but ... the problem does not
>occur when using the BDE. So, I will post in two Newsgroups.
>
> The tRzDBComboxBox is a Raize version of the tDBComboxBox, with the extra
> feature that besides a given set of 'Items' they have a 'Values' property,
> which (if defined) is a set of strings that are stored in the database
> instead of the corresponding 'item'. So, you can show items 'Amex' or
> 'Visa', but store values 'A' or 'V' respectively
>
> We have an tRzDBComboBox that offers its field six Value/Item combinations
> (all with value <> item). All records have a non-null value that is in the
> Values list.
>
> (1) when the app starts up on record 1 of the table involved, the combo is
> blank.
>
> (2) when you scroll to subsequent records, the control shows 'values'
> (should be 'items') as long as all visited records have the first possible
> value.
>
> (3) It switches to showing 'items' (which is correct) as soon as you hit a
> record with a value that is not the very first possibility.
>
> When using a tRzDBComboBox without defining 'Values', we still get an
> empty control when starting on record 1. (So, we may have two separate
> problems here.)
>
> All working fine when we use the BDE. Now where is the issue?
>
> RJ
>
>