subform (again)

[Franco Fornari]

Hello,

sorry if I bother you again with these questions, but I'd need to know
if I have to file one or more issues (unless someone already did it) or,
instead,  it's a matter of my lack of experience.

Subforms:

   1. A query with one or more calculated fields doesn't work if used as
      source for a subform grid. The same query alone works perfectly.
   2. I'm not able to call any macro by en event from inside any column
      (receiving focus, i.e.) of a subform grid. It seems something like
      what is described in the issue 60604, wich is formally closed as
      fixed.
   3. In subform grids, Standard Values (default) don't work.

Reports:

   1. Fixed lines: I'm not able to draw any vertical line, only
      orizontal. Or, better, I can see a vertical line drawn in Report
      Designer window, but it disappear in Report preview.
   2. Fixed lines: Users can change colors for any report's object but
      fixed lines. They are black, only. This seems to need an enhancement.

Please, can someone tell me if, and where, I'm right/wrong?

Thanks in advance,
Franco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Fernand Vanrie]

Franco Fornari wrote:

> Hello,
>
> sorry if I bother you again with these questions, but I'd need to know
> if I have to file one or more issues (unless someone already did it)
> or, instead,  it's a matter of my lack of experience.
>
> Subforms:
>
>   1. A query with one or more calculated fields doesn't work if used as
>      source for a subform grid. The same query alone works perfectly.
>   2. I'm not able to call any macro by en event from inside any column
>      (receiving focus, i.e.) of a subform grid. It seems something like
>      what is described in the issue 60604, wich is formally closed as

a new one 98973 is now in "UNCONFIRMED"

>      fixed.
>   3. In subform grids, Standard Values (default) don't work.
>
> Reports:
>
>   1. Fixed lines: I'm not able to draw any vertical line, only
>      orizontal. Or, better, I can see a vertical line drawn in Report
>      Designer window, but it disappear in Report preview.
>   2. Fixed lines: Users can change colors for any report's object but
>      fixed lines. They are black, only. This seems to need an
> enhancement.
>
> Please, can someone tell me if, and where, I'm right/wrong?
>
> Thanks in advance,
> Franco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Fernand Vanrie]

Franco Fornari wrote:

> Hello,
>
> sorry if I bother you again with these questions, but I'd need to know
> if I have to file one or more issues (unless someone already did it)
> or, instead,  it's a matter of my lack of experience.
>
> Subforms:
>
>   1. A query with one or more calculated fields doesn't work if used as
>      source for a subform grid. The same query alone works perfectly.

smell's like the UNCONFIRMED 102793

>   2. I'm not able to call any macro by en event from inside any column
>      (receiving focus, i.e.) of a subform grid. It seems something like
>      what is described in the issue 60604, wich is formally closed as
>      fixed.
>   3. In subform grids, Standard Values (default) don't work.
>
> Reports:
>
>   1. Fixed lines: I'm not able to draw any vertical line, only
>      orizontal. Or, better, I can see a vertical line drawn in Report
>      Designer window, but it disappear in Report preview.
>   2. Fixed lines: Users can change colors for any report's object but
>      fixed lines. They are black, only. This seems to need an
> enhancement.
>
> Please, can someone tell me if, and where, I'm right/wrong?
>
> Thanks in advance,
> Franco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

Hello Fernand,

thanks for your quick reply. As for the Issues 60604 = 98973 I think
that the problem is exactly the same, you are right. Less sure about the
bug described in Issue 102793, first of all because I'm using the
embedded HSQLDB and, then, because in that Issue there is no mention
about calculated fields.

Thanks again,
Franco

Fernand Vanrie ha scritto:

> Franco Fornari wrote:
>> Hello,
>>
>> sorry if I bother you again with these questions, but I'd need to
>> know if I have to file one or more issues (unless someone already did
>> it) or, instead,  it's a matter of my lack of experience.
>>
>> Subforms:
>>
>>   1. A query with one or more calculated fields doesn't work if used as
>>      source for a subform grid. The same query alone works perfectly.
> smell's like the UNCONFIRMED 102793
>>   2. I'm not able to call any macro by en event from inside any column
>>      (receiving focus, i.e.) of a subform grid. It seems something like
>>      what is described in the issue 60604, wich is formally closed as
>>      fixed.
>>   3. In subform grids, Standard Values (default) don't work.
>>
>> Reports:
>>
>>   1. Fixed lines: I'm not able to draw any vertical line, only
>>      orizontal. Or, better, I can see a vertical line drawn in Report
>>      Designer window, but it disappear in Report preview.
>>   2. Fixed lines: Users can change colors for any report's object but
>>      fixed lines. They are black, only. This seems to need an
>> enhancement.
>>
>> Please, can someone tell me if, and where, I'm right/wrong?
>>
>> Thanks in advance,
>> Franco
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
> ------------------------------------------------------------------------
>
>
> Nessun virus nel messaggio in arrivo.
> Controllato da AVG - www.avg.com
> Versione: 8.5.387 / Database dei virus: 270.13.58/2309 -  Data di rilascio: 08/17/09 06:08:00
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Frank Schoenheit, Sun Microsystems Germany]

Hi Franco,

>    1. A query with one or more calculated fields doesn't work if used as
>       source for a subform grid. The same query alone works perfectly.

Cannot reproduce. How is your setup, exactly?

>    2. I'm not able to call any macro by en event from inside any column
>       (receiving focus, i.e.) of a subform grid. It seems something like
>       what is described in the issue 60604, wich is formally closed as
>       fixed.

Well, yes ... as written in the issue, looking into the code, it seems
there has *never ever* been any code for supporting this for table
columns. Basically, the events slipped into the property browser by
accident :)
Nonetheless, it makes sense implementing them.

>    3. In subform grids, Standard Values (default) don't work.

Cannot reproduce. Again, can you elaborate, please?

>    1. Fixed lines: I'm not able to draw any vertical line, only
>       orizontal. Or, better, I can see a vertical line drawn in Report
>       Designer window, but it disappear in Report preview.

http://www.openoffice.org/issues/show_bug.cgi?id=104447

>    2. Fixed lines: Users can change colors for any report's object but
>       fixed lines. They are black, only. This seems to need an enhancement.

Feel free to submit one :)
Though I am not sure we should invest into the current lines, they have
some other quirks, too, so I think they should be re-implemented to be
more like the lines in e.g. Draw.

Ciao
Frank

--
- Frank Schönheit, Software Engineer         frank.schoenheit@... -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

Hi Frank,

since in the meantime I ran into other troubles, here is a new summary
of all what I found, with the clarifications (I hope :-) ) you asked me:

I'm using OpenOffice 3.1 Official Release with Win XP Pro

Forms:

SELECT "TipoDoc", "NumDoc", "DataReg", "IdCont", "Causale", "Parcella",
"AliqIVA", "Parcella" * "AliqIVA" / 100 AS "IVA" FROM "Avere" AS "Avere"
WHERE ( "TipoDoc" = 'PAE' OR "TipoDoc" = 'PAI' )

   1. This query is editable if used alone, also having a calculated
      field. But as source of a subform grid, linked to main form by
      "IdCont", it doesn't work anymore. "IVA" is the calculated field I
      need for checking data only. The program doesn't execute the query
      but prompts for data input also for that field. Removing IVA
      column fron grid, all work fine.
   2. In any column of a subform grid, it's possible to pre-set a
      default value (Standard Value) like in table fields. That's true
      in theory, however, because if I set "AliqIVA" to 0, or 20, or to
      whatever else number, the subform grid doesn't work anymore.
      Without any calculated fields, obviously.

Reports:

   1. In a report, I need to group data by quarter (date), but it
      doesn't work. If you select "quarter" in Sorting and Grouping
      window, in fact the program groups data on month and, if you close
      and reopen the report, you find the Group settled on "month", not
      on "quarter".
   2. Drag and drop fields between report sections is really a pain.
      Fields disappear or seem to go random. Mouse position is
      absolutely not reliable. Same thing if you try to resize a field
      or a fixed line. Often, when trying to move a field to the right
      side, the entire report shifts to the opposite and I cannot
      realize the actual position I am.
   3. Labels have vertical alignement, too, but it really doesn't work.
      If you set it to "center", i.e., when reopening report, vertical
      alignement is settled to "standard" again.
   4. Fixed Lines cannot cross each other. This is a hard restriction
      for any layout.


Finally, about fixed lines, if they will be more widely re-implemented,
as you told me, perhaps it cannot worth that I file an issue for a
limited enhancement like colors, isn't?

Thanks in advance,
Franco

Frank Schoenheit, Sun Microsystems Germany ha scritto:
> Hi Franco,
>
>  
>>    1. A query with one or more calculated fields doesn't work if used as
>>       source for a subform grid. The same query alone works perfectly.
>>    
>
> Cannot reproduce. How is your setup, exactly?
>  

>  
>>    2. I'm not able to call any macro by en event from inside any column
>>       (receiving focus, i.e.) of a subform grid. It seems something like
>>       what is described in the issue 60604, wich is formally closed as
>>       fixed.
>>    
>
> Well, yes ... as written in the issue, looking into the code, it seems
> there has *never ever* been any code for supporting this for table
> columns. Basically, the events slipped into the property browser by
> accident :)
> Nonetheless, it makes sense implementing them.
>
>  
>>    3. In subform grids, Standard Values (default) don't work.
>>    
>
> Cannot reproduce. Again, can you elaborate, please?
>
>  
>>    1. Fixed lines: I'm not able to draw any vertical line, only
>>       orizontal. Or, better, I can see a vertical line drawn in Report
>>       Designer window, but it disappear in Report preview.
>>    
>
> http://www.openoffice.org/issues/show_bug.cgi?id=104447
>
>  
>>    2. Fixed lines: Users can change colors for any report's object but
>>       fixed lines. They are black, only. This seems to need an enhancement.
>>    
>
> Feel free to submit one :)
> Though I am not sure we should invest into the current lines, they have
> some other quirks, too, so I think they should be re-implemented to be
> more like the lines in e.g. Draw.
>
> Ciao
> Frank
>
>  
> ------------------------------------------------------------------------
>
>
> Nessun virus nel messaggio in arrivo.
> Controllato da AVG - www.avg.com
> Versione: 8.5.387 / Database dei virus: 270.13.65/2322 -  Data di rilascio: 08/23/09 18:03:00
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Frank Schoenheit, Sun Microsystems Germany]

Hi Franco,

some quick comments for the moment:

>    2. In any column of a subform grid, it's possible to pre-set a
>       default value (Standard Value) like in table fields. That's true
>       in theory, however, because if I set "AliqIVA" to 0, or 20, or to
>       whatever else number, the subform grid doesn't work anymore.
>       Without any calculated fields, obviously.

how does "doesn't work" manifest? No data displayed? Crash? Wrong data
displayed? No default value displayed?

> Reports:
>
>    1. In a report, I need to group data by quarter (date), but it
>       doesn't work. If you select "quarter" in Sorting and Grouping
>       window, in fact the program groups data on month and, if you close
>       and reopen the report, you find the Group settled on "month", not
>       on "quarter".

That certainly sounds like you should visit IssueZilla here :)

>    3. Labels have vertical alignement, too, but it really doesn't work.
>       If you set it to "center", i.e., when reopening report, vertical
>       alignement is settled to "standard" again.

Issue 99058, fixed in CWS dba32f.

>    4. Fixed Lines cannot cross each other. This is a hard restriction
>       for any layout.
>
>
> Finally, about fixed lines, if they will be more widely re-implemented,
> as you told me, perhaps it cannot worth that I file an issue for a
> limited enhancement like colors, isn't?

I didn't say they "will be" more widely implemented, I said they have a
lot of problems and "should be" re-implemented on another base :)
Whether and when this happens depends on a lot of factors - amongst
others, a high number of issues in IZ regarding lines increases the
chances of them being improved :)

Ciao
Frank

--
- Frank Schönheit, Software Engineer         frank.schoenheit@... -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

Hi Frank,

Frank Schoenheit, Sun Microsystems Germany ha scritto:

> Hi Franco,
>
> some quick comments for the moment:
>
>  
>>    2. In any column of a subform grid, it's possible to pre-set a
>>       default value (Standard Value) like in table fields. That's true
>>       in theory, however, because if I set "AliqIVA" to 0, or 20, or to
>>       whatever else number, the subform grid doesn't work anymore.
>>       Without any calculated fields, obviously.
>>    
>
> how does "doesn't work" manifest? No data displayed? Crash? Wrong data
> displayed? No default value displayed?
>  

Sorry, you are right. Default value is displayed, but when I press enter
to write the new record, the program warn me that I'm trying to insert
NULL in a column that does not allow NULL values. In fact it doesn't
matter if that fields is settled to accept NULL values or not, in table
field or in grid column or both.

>  
>> Reports:
>>
>>    1. In a report, I need to group data by quarter (date), but it
>>       doesn't work. If you select "quarter" in Sorting and Grouping
>>       window, in fact the program groups data on month and, if you close
>>       and reopen the report, you find the Group settled on "month", not
>>       on "quarter".
>>    
>
> That certainly sounds like you should visit IssueZilla here :)
>  

Ok!
>  
>>    3. Labels have vertical alignement, too, but it really doesn't work.
>>       If you set it to "center", i.e., when reopening report, vertical
>>       alignement is settled to "standard" again.
>>    
>
> Issue 99058, fixed in CWS dba32f.
>  
Great!

>  
>>    4. Fixed Lines cannot cross each other. This is a hard restriction
>>       for any layout.
>>
>>
>> Finally, about fixed lines, if they will be more widely re-implemented,
>> as you told me, perhaps it cannot worth that I file an issue for a
>> limited enhancement like colors, isn't?
>>    
>
> I didn't say they "will be" more widely implemented, I said they have a
> lot of problems and "should be" re-implemented on another base :)
> Whether and when this happens depends on a lot of factors - amongst
> others, a high number of issues in IZ regarding lines increases the
> chances of them being improved :)
>
> Ciao
> Frank
>  

Ok, roger. I'll file a number of them :-)
>  
> ------------------------------------------------------------------------
>
>
> Nessun virus nel messaggio in arrivo.
> Controllato da AVG - www.avg.com
> Versione: 8.5.387 / Database dei virus: 270.13.65/2322 -  Data di rilascio: 08/23/09 18:03:00
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Frank Schoenheit, Sun Microsystems Germany]

Hi Franco,

again a quick response to one particular item, your other mail has to
wait a little longer for /me finding more time ...

>>>    2. In any column of a subform grid, it's possible to pre-set a
>>>       default value (Standard Value) like in table fields. That's true
>>>       in theory, however, because if I set "AliqIVA" to 0, or 20, or to
>>>       whatever else number, the subform grid doesn't work anymore.
>>>       Without any calculated fields, obviously.
>>>    
>> how does "doesn't work" manifest? No data displayed? Crash? Wrong data
>> displayed? No default value displayed?
>>  
> Sorry, you are right. Default value is displayed, but when I press enter
> to write the new record, the program warn me that I'm trying to insert
> NULL in a column that does not allow NULL values.

Hmm. Can you set up a small sample (HSQLDB) .odb which demonstrates
this? And submit it to IZ? :)

Yes, I say this pretty often :), but in fact issues in IZ, ideally with
a "just-click-here-and-see-the-problem"-attachment, have better chances
for us developers/QA diving into the problem.

An in cases like those, it sounds pretty much like a bug, so IZ finally
is the right place, anyway.

Cia
Frank

--
- Frank Schönheit, Software Engineer         frank.schoenheit@... -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

Hi Frank,

no problem, but I'll set up a sample db that allows you to check all
issues I pointed out. In case, I'll use it for more then one issue, ok?

Thanks,
Franco


Frank Schoenheit, Sun Microsystems Germany ha scritto:

> Hi Franco,
>
> again a quick response to one particular item, your other mail has to
> wait a little longer for /me finding more time ...
>
>  
>>>>    2. In any column of a subform grid, it's possible to pre-set a
>>>>       default value (Standard Value) like in table fields. That's true
>>>>       in theory, however, because if I set "AliqIVA" to 0, or 20, or to
>>>>       whatever else number, the subform grid doesn't work anymore.
>>>>       Without any calculated fields, obviously.
>>>>    
>>>>        
>>> how does "doesn't work" manifest? No data displayed? Crash? Wrong data
>>> displayed? No default value displayed?
>>>  
>>>      
>> Sorry, you are right. Default value is displayed, but when I press enter
>> to write the new record, the program warn me that I'm trying to insert
>> NULL in a column that does not allow NULL values.
>>    
>
> Hmm. Can you set up a small sample (HSQLDB) .odb which demonstrates
> this? And submit it to IZ? :)
>
> Yes, I say this pretty often :), but in fact issues in IZ, ideally with
> a "just-click-here-and-see-the-problem"-attachment, have better chances
> for us developers/QA diving into the problem.
>
> An in cases like those, it sounds pretty much like a bug, so IZ finally
> is the right place, anyway.
>
> Cia
> Frank
>
>  
> ------------------------------------------------------------------------
>
>
> 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: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Frank Schoenheit, Sun Microsystems Germany]

Hi Franco,

> no problem, but I'll set up a sample db that allows you to check all
> issues I pointed out. In case, I'll use it for more then one issue, ok?

fine with me.

Thanks & Ciao
Frank

--
- Frank Schönheit, Software Engineer         frank.schoenheit@... -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

Hi Frank,

I don't know what happened with my previous message, anyway here is the
text.

here is the sample db I settled up. For the privacy I removed any fields
and data relating to persons, leaving numbers, only.
Maybe you can first check the issues I pointed out and select wich of
them are really bugs.

As for the subform grid, with this set up it works. "Num Doc" field is
an Auto-Increment one and it works fine. There are several records
already registered for many people, but others haven't any.
Fill up "Tipo Doc" with "PAE" or "PAI", "Data Reg" with a date,
"Parcella" with an amount.  Now, if you try to insert an integer (0 to
20, i.e.) into "AliqIVA" you will be able to add a new record, but if
you set that field from 0 to 20 as default, you'll get an error.

Moreover, if you try to add a calculated field as column in the subform
grid, i.e. "Parcella" * "AliqIVA" / 100, you'll get another error.

As for the report, it works as it is, but you can easily check all the
issues I described in my previous emails.

P.S. Is it possible to tell people wich take care of the italian version
of OpenOffice, that the correct translation of 1th, 2nd, 3rd, etc. is
not 1o, 2o, 3o, ..., but 1°, 2°, 3°, ...?  You can see this also in my
report, where 1th quarter (or 2nd, 3rd) become 1o (2o, 3o, ... )
trimestre. Very ugly. :-(

Thanks in advance,
Franco

Frank Schoenheit, Sun Microsystems Germany ha scritto:

> Hi Franco,
>
>  
>> no problem, but I'll set up a sample db that allows you to check all
>> issues I pointed out. In case, I'll use it for more then one issue, ok?
>>    
>
> fine with me.
>
> Thanks & Ciao
> Frank
>
>  
> ------------------------------------------------------------------------
>
>
> 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: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Frank Schoenheit, Sun Microsystems Germany]

Hi Franco,

> P.S. Is it possible to tell people wich take care of the italian version
> of OpenOffice, that the correct translation of 1th, 2nd, 3rd, etc. is
> not 1o, 2o, 3o, ..., but 1°, 2°, 3°, ...?

I do not know who's responsible for the Italian translation, but reading
(ehm, not really) http://it.openoffice.org/localizzazione/index.html I
think that a mail to localizzazione@... might help.

Ciao
Frank

--
- Frank Schönheit, Software Engineer         frank.schoenheit@... -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Fernand Vanrie]

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: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

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: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
> ------------------------------------------------------------------------
>
>
> 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: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Fernand Vanrie]

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: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>> ------------------------------------------------------------------------
>>
>>
>> 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: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Franco Fornari]

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: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> 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: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
> ------------------------------------------------------------------------
>
>
> 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: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Frank Schoenheit, Sun Microsystems Germany]

Hi Fernand,

still without having looked at Franco's sample DB ....

> 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.

There's not really a compelling reason why sub forms should not work
with calculated fields or default values, neither technical nor
conceptual. The approach has its limits, for instance, queries over
multiple tables are not updatable, but this doesn't depend on their
usage in sub forms.

Ciao
Frank

--
- Frank Schönheit, Software Engineer         frank.schoenheit@... -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Fernand Vanrie]

Frank ,Franco

Indead "one  table" query's works

Calculated fields works also if the "column" properties of the form
control are set to "Input NOT required" and "prevent data entry"

Greetz
Fernand

> Hi Fernand,
>
> still without having looked at Franco's sample DB ....
>
>  
>> 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.
>>    
>
> There's not really a compelling reason why sub forms should not work
> with calculated fields or default values, neither technical nor
> conceptual. The approach has its limits, for instance, queries over
> multiple tables are not updatable, but this doesn't depend on their
> usage in sub forms.
>
> Ciao
> Frank
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...