Error (8)

[Dave (coloniesonline.co.uk)]

I had a problem with the error (8), but after looking at the
debug option info. It seems that I have been using
the wrong field.. Example:
I had two tables main table being reptype and
the other being old_categories.
I had two fields in reptype one called cat_id
and the other called category. cat_id is a
primary field and category is a varchar to
hold the category description. I created the
other table old_categories to allow choice
in a single choice menu. This worked fine under
2.x, but under 3.x I had problems namely the
(8) error. I made the mistake of turning the
category text field into the single choice
field and linking to the cat_id in the
old_categories table to the cat_id in the main
table reptype. This gave me a error, since
Dadabik linked my text field reptype.categories to
old_categories.cat_id. So I changed the choice field
to reptype.cat_id and now it works. I have removed
the category text field from reptype since it
is no longer needed.
Hope this helps some people.
Dave

 

[DanW]

Thanks for the info, but I'm Still unclear. Perhaps you can tell/show me where you made the change:

Lets have an example:

-----MAIN TABLE --------
| M_ID | TOPIC |
------------------------

-----Support TABLE------
| S_ID | Topic_choices|
------------------------

Both Tables have ID set as primary key - auto index.
BOth Tables Topic & Topic choices are varchar


MAIN TABLE - field/column TOPIC should be single choice ( next release -perhaps back to multiple choices ---- and the "selections" are based upon entires from the Support table - column Topic_choices.



SO we now are in the interface configurator...(Admin)

MAIN TABLE
Name Of Field: Topic
Field Type: Select_single
Primary key field:
Primary key table:
Linked Fields:

- Now based upon older versions , I would populate the fields as follows


MAIN TABLE
Name Of Field: Topic
Field Type: Select_single
Primary key field: S_ID
Primary key table: Support
Linked Fields: Topic_Choices


This works fine for Selecting any available entry that is listed in the support table, but a "show all" results in the error.

Can you fill in the below template with the correct values?

Thanks in advance,
dan ( and the few "others" )



MAIN TABLE
Name Of Field: Topic
Field Type:
Primary key field:
Primary key table:
Linked Fields:

 

[Rafael Alvarado]

I get the same thing, please anyone !!

 

[Eugenio]

DanW wrote:

> Thanks for the info, but I'm Still unclear. Perhaps you can
> tell/show me where you made the change:
>
> Lets have an example:
>
> -----MAIN TABLE --------
> | M_ID | TOPIC |
> ------------------------
>
> -----Support TABLE------
> | S_ID | Topic_choices|
> ------------------------
>
> Both Tables have ID set as primary key - auto index.
> BOth Tables Topic & Topic choices are varchar

[...]

the field topic in the main table must be numeric, not varchar, because it contains the corresponding S_ID value.



(Latest version of DaDaBIK when this message was posted: 3.0 beta)