Andrew B
|
| Posted: 02/04/2002, 10:15 PM |
|
I think i have found a bug. Perhaps one of you kind ppl. at codecharge can verify?
When I create a record form and provide custom SQL to that record form (it is display only), the form pulls from the custom SQL for the field list, but does not use that SQL to actually open the recordset.
Easy for me to replicate :
1. create record type form, give it a table.
2. enter custom sql to select (select count(*) as f from table)
3. 'f' will be in field list. Try to run the form
error : 'invalid column name 'f''
There does not appear to be any way to fix this.
I can get around it by using a grid. Grids are bad, they draw the colum header row even if there are NO column headers for ANY of the columns (1, in this case).
The only way I found around it was to use a 'menu', and manually set the 'fldBlahBlah' values.
|
|
|
 |
Alex Alexapolsky
|
| Posted: 02/05/2002, 4:39 AM |
|
Record forms don't use cusom sql by default.
That's an expected behavour. Records have nothing special to do
with custom selects. All that can be done concerning locating a record
may be done in Form/Input properties.Custom sql is redundant and is not
supposed to work.
|
|
|
|
Andrew B
|
| Posted: 02/05/2002, 9:43 PM |
|
Ok...
The reason I would like this is that there are often times where I NEED to use the record form layout. I remember trying to do it with a grid, but can't recall why it did not work.
Maybe we need a more flexible form type, for display only? Like a menu type on steroids.
|
|
|
|
|
