Proper syntax table.field or filed.table BUG in form designer?

[JD Kromkowski]

What’s the deal with this: is it TABLE.field or field.TABLE For a filter for example, it is TABLE.field = “myfield” But if I “modify” form, in the form designer the field editboxes are displayed field.TABLE JDK

[Michael]

On 08/04/2013 13:56, kromkowski wrote:
> What's the deal with this:
>
> is it TABLE.field or field.TABLE
>
>
> For a filter for example, it is
>
> TABLE.field = "myfield"
>
> But if I "modify" form, in the form designer the field editboxes are
> displayed
>
> field.TABLE
>
> JDK
>

The syntax for queries is Table.Field. We decided to add this additional information for bound edit and text controls in the most
recent revision, and after careful consideration went for Field.Table, mainly because if something gets cut off, it is better to
be the table name than the field name.

Ciao, Neil

[JD Kromkowski]

OK. I had worked very hard to rid myself of thinking anyway but
TABLE.field, so there was some momentary self doubt about what I was
seeing and whether I had trained my self completely wrong.

If there is any best practice, I recommend:

datasources – lower case "mydata"
tables – UPPERCASE "MYTABLE"
fields – (I try but am not totally consistent – Initial Caps)
"Myfield" or "MyField"

JDK

On 04/08/13 2:13 PM, Neil Robinson wrote:
> On 08/04/2013 13:56, kromkowski wrote:
>> What's the deal with this:
>>
>> is it TABLE.field or field.TABLE
>>
>>
>> For a filter for example, it is
>>
>> TABLE.field = "myfield"
>>
>> But if I "modify" form, in the form designer the field editboxes are
>> displayed
>>
>> field.TABLE
>>
>> JDK
>>
>
> The syntax for queries is Table.Field. We decided to add this additional information for bound edit and text controls in the most
> recent revision, and after careful consideration went for Field.Table, mainly because if something gets cut off, it is better to
> be the table name than the field name.
>
> Ciao, Neil
>

[Author]

Posts