V9 with SqlServer: can field names omit the underscore character?

[rmcgaffic]

If you use active link tables with V9, can you create a default form without underscore characters in the labels?

The active link to SQLServer tables looks very interesting, I wonder if this new capability allows users to overcome a small, but enormously annoying, behavior of V8 using dbf files.

When you attempt to create a table field in V8 with dbf, an underscore is automatically inserted:

You type: Last name
A5 enters: Last_name

When you create a form based on this table using A5's default form (contains all the fields in the table/set), the labels for field also have the underscore character.

Last_name LAST_NAME

If you want to make your form easy to read, you have to manually edit out the underscore character in the label to simply Last name.

I know SQLServer will permit spaces in field name. This is also the case with Microsoft Access 2003.

[Selwyn Rabins]

Re: V9 with SqlServer: can field names omit the underscore character?

Sorry for duplicate posting

not sure i understand the question.

are you asking about an active link table on a sql server table that has a space in a field name?

if so, the active link table will replace the space with an underscore as a5 does not allow spaces in field names.

[Tim Kiebert]

Re: V9 with SqlServer: can field names omit the underscore character?

Robert,

If you go into field rules after creating the table and give each field a Default descriptive name then this is what is used for form labels and browse columns. I am pretty sure that the no spaces issue is a dbf format characteristic. And an active table in Alpha is still a dbf.


From the help

Default Descriptive Name
Use Default Descriptive Names when you want to provide longer, helpful descriptions of fields for users. Default Descriptive Names replace standard field labels on layouts.
For example, if a table has a field called CUSTOMER_NUMBER, you could change the Default Descriptive Name to "Customer ID#." Alpha Five displays "Customer ID#" as field labels on forms and browses, but the actual field name is still CUSTOMER_NUMBER.
Default Descriptive Names can be especially useful if you create several layouts for a table. You only type in a Default Descriptive Name once, rather than editing field labels for every layout.

[rmcgaffic]

Re: V9 with SqlServer: can field names omit the underscore character?

Tim,

Thanks. I tried your suggestion and it works, but I am still disappointed by the result.

I changed the default descriptive name and the field description to
Last name

Here's what I got with my form--
Last name:

If I wanted a colon at the end of the label, I would have typed one in.

So unfortunately I have to edit each and every label to remove the :

The colon at the end of a label was in vogue in the 70's and 80's when character based interfaces were the only options, and the colon was used to separate the label from the text field I just wish Alpha Five would realize that this is 2008 and we have different colors and fonts that accomplish the same objective.

Wouuldn't it be nice if on the same field rules screen where the descriptive name and field description are maintained, there was an option (checkbox) to omit or use a colon?

Or better yet, make the colon assignment to labels a part of the style sheet specification?

I am trying to emulate the ultra-cool vertical grid used by Intuit in its Customer Service Manager software. The good news is that A5's allows me the control to do what I could not with FileMaker, and could do only with moderate difficulty with MS Access 2007.

Intuit's design allows a maximum of information to be presented on a page and yet not appear overcrowded. For those of us who are totally put off by MS Office 2007's grab for screen real estate with "ribbons" (kiss 20% of your screen goodbye), Intuit's approach helps to minimize the number of screens required to display long or complex master records.

Bob
Pittsburgh

[CALocklin]

Re: V9 with SqlServer: can field names omit the underscore character?

Bob, I'd be interested in seeing a screenshot of Intuit's layout.

[Selwyn Rabins]

Re: V9 with SqlServer: can field names omit the underscore character?

Tim,

Thanks. I tried your suggestion and it works, but I am still disappointed by the result.

I changed the default descriptive name and the field description to
Last name

Here's what I got with my form--
Last name:

If I wanted a colon at the end of the label, I would have typed one in.

So unfortunately I have to edit each and every label to remove the :

The colon at the end of a label was in vogue in the 70's and 80's when character based interfaces were the only options, and the colon was used to separate the label from the text field I just wish Alpha Five would realize that this is 2008 and we have different colors and fonts that accomplish the same objective.

Wouuldn't it be nice if on the same field rules screen where the descriptive name and field description are maintained, there was an option (checkbox) to omit or use a colon?

Or better yet, make the colon assignment to labels a part of the style sheet specification?

I am trying to emulate the ultra-cool vertical grid used by Intuit in its Customer Service Manager software. The good news is that A5's allows me the control to do what I could not with FileMaker, and could do only with moderate difficulty with MS Access 2007.

Intuit's design allows a maximum of information to be presented on a page and yet not appear overcrowded. For those of us who are totally put off by MS Office 2007's grab for screen real estate with "ribbons" (kiss 20% of your screen goodbye), Intuit's approach helps to minimize the number of screens required to display long or complex master records.

Bob
Pittsburgh

we agree that the colon is antiquated. we have removed it. the default form and form genie no longer put in colons in field labels.

[CALocklin]

Re: V9 with SqlServer: can field names omit the underscore character?

I sure wish you could have made the colon optional. Presumably this change won't affect existing labels. However, some of us still have old apps to work with and will be having to add it back in when making minor changes on old stuff. (Let's see, do I want to make this one new field label look like the other 40 on this form and all the ones on the other 70 forms or do I want to go change all the labels on all the other forms? I wonder which one the customer would be willing to pay for!?)

And, yes, I can add it in but the Bob could just as easily have deleted it.

Since my current field naming method usually requires re-typing the labels (which I suspect most people usually ended up doing much of the time anyway) I guess one more key press won't make any real difference on new apps.

[Selwyn Rabins]

Re: V9 with SqlServer: can field names omit the underscore character?

I sure wish you could have made the colon optional. Presumably this change won't affect existing labels. However, some of us still have old apps to work with and will be having to add it back in when making minor changes on old stuff. (Let's see, do I want to make this one new field label look like the other 40 on this form and all the ones on the other 70 forms or do I want to go change all the labels on all the other forms? I wonder which one the customer would be willing to pay for!?)

And, yes, I can add it in but the Bob could just as easily have deleted it.

Since my current field naming method usually requires re-typing the labels (which I suspect most people usually ended up doing much of the time anyway) I guess one more key press won't make any real difference on new apps.

it is. there is a new setting in view, settings, preferences, forms, label terminator.

[CALocklin]

Re: V9 with SqlServer: can field names omit the underscore character?

it is. there is a new setting in view, settings, preferences, forms, label terminator.

Cool! Thanks.