Hi Fernand,
macros you saw are only trials for the moment and are useless for this
sample db. I simply forgot to delete them. Please, forget them you too.
Using query as datasource for subforms is allowed by design. Better, by
design you can choose among table, query or SQL command, then my choice
is not a mistake.
You don't consider that my source query works fine if used alone also
with one or more calculated fields, then, why not also in a subform?
Generally speaking, I think that a user should be allowed to make
anything wich is not explicitly forbidden, not the opposite, don't you mind?
Greetings,
Franco
Fernand Vanrie ha scritto:
Franco Fornari wrote:
Hi Fernand,
you sent me complicated suggestions.
I saw you used already some "complicated macro's , make a dialog, fill
the fields with the data from a sql statement , play around with the
data in the fields, send them back with a other SQL statement to your
tables...
Why using a query as source for a subform is a mistake?
OK: see a Query as a temporary "view" on data stored in one or more
tables but you can not store data in "query" only in a "table" see a
Form as support to "view" and/or to "store" data in "tables" ,
"querys ,views or resultsets from a SQL command". can only been used
to "view" this data. When based on a table then the database engine
can send new or altered data to this table. When using a query, view
or SQL command as datasource you need some macro code (SQL stements)
to send the data to a table.
Without calculated fields it works fine. And why, without any
calculated fields in subform,
the calculated fields are comming from a "query" and you try to enter
it in a table where there is simply no field for it
I cannot use some default values in columns? Default values are there
by design.
Yes you can use simple default values but I think you try to enter a
formula or a range
If the program has some limits,
Yes, but the wrong use has also his limits :-)
hope it helps
Fernand
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]
---------------------------------------------------------------------
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]
