Manolis Christodoulou wrote:
Drew Jensen wrote:
It is possible that you are constructing your form/sub-form
improperly. The select statement you show above is using a
replaceable named parameter ":link_from_idfield" which is proper if
you want to have the system prompt you for a value interactively. It
is incorrect for use as a sub-form data source.
When building the form you would need only this select statement:
SELECT * FROM "mydatabase"."datailtable"
Then in the form designer you would define the link between the main
- sub forms. I take it that in your case the link is something akin to:
"mastertable"."idfield" --> "detailtable"."idfield"
I do not construct any SQL by hand. I do exactly as you are describing
above. I link the forms from the form properties window. This strange
error appears also with old forms that used to work fine with MySQL
ODBC 3.51 driver and with the JDBC driver.
My mistake - just tried generating a form/Sub-form using the wizard -
wizard is just messed up when you designate that you want a sub form.
After fixing the link by hand and trying to open...same exact error as
you are getting.
OK at that point I wondered if it might have something to do with
relationships, as the relationship winodw will not open either. So I
attempted to add overrideSupportsIntegrityEnhancementFacility=TRUE to
the driver configuration as one does with the JDBC dirver. The driver
will not recognize that option and fails to connect at all.
Then I wondered if ISAM vs InnoDB might have something to with it.
I used MySQL Administrator to create a new schema, a couple of tables
using innodb and a proper foreign key between them and returned to base
to try to form designer again - no difference.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
