Hi Fernand,
you sent me complicated suggestions. Why using a query as source for a
subform is a mistake? Without calculated fields it works fine. And why,
without any calculated fields in subform, I cannot use some default
values in columns? Default values are there by design.
If the program has some limits, they should be pointed out. A workaround
is not the best way to go, in my opinion. At the most it can be a
temporary solution.
Best,
Franco
Fernand Vanrie ha scritto:
Franco, Frank
I just checked (out of curiosity how others use OO-base) the
db_sample_franco dbase.
I only can reproduce the Calculated field error, who is no error but a
mistake from Franco who uses a query as a datasource for a subForm.
Franco: change the datasource to the table where the Form-data must
been inserted and forgot the calculated field.
If you want to uses calculated fields then you are better off using a
Dialog and a macro to collect the data and then using a macro to
pass the data to the tables.
With a Dialog and some macro's you can check (Default values) and
manipulate all the data without restrictions, as soon all data is
checked then pass them to the Table
Hope it helps
Fernand
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
------------------------------------------------------------------------
Nessun virus nel messaggio in arrivo.
Controllato da AVG - www.avg.com
Versione: 8.5.387 / Database dei virus: 270.13.65/2324 - Data di rilascio: 08/24/09 12:55:00
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]