Drew Jensen wrote:
Sub title to this post - Sometimes unintended consequences work out
for the good!
There are a couple of threads dealing with Base over all that I have
been both wanting to comment on and avoiding as I know that at times I
seem to just hit the negative.
Current problem - you can not update a query that does much of
anything beyond select fields from a single table. ( and that is a
problem )
But today I tried something using the new property "Form checks input
for required fields" and found my unintended consequence. ( UC )
The following select statement in a query
SELECT "InvoiceDetails".*, "Quantity" * "UnitPrice" AS "LineTotal"
FROM "InvoiceDetails" AS "InvoiceDetails"
In OO.o <= 2.3.1 use that query with a table grid control you can not
update the records, because of that calculated column.
With the new property set to FALSE - you can!
It is about time one of those UC's went the right way.
Drew
Please for anyone that wants to explain all that select statements
that still are read only - don;t. Let's just enjoy this for a moment.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm sorry - I was wrong. This does not work. I forgot that it will
allowed updates to records in this situation but not inserts. The new
property has no effect on this, it still fails on insert.
Damn it...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
