Number fields Blank Title 103986

Yahoo Archive
1
So I see this setting works for fields, but it doesn't appear to work for tableviews (Lists) of data. Is there another setting that will make that work?



--- In vantage@yahoogroups.com, "jgiese1988" <jgiese@...> wrote:
>
> Wow duh of course why did I look there... For global config changes like that can I just unzip the clientrelease zip on the server make the change and rezip it, that way when people get it installed it has those changes right away? How can we push that to clients with it already installed or is this a manual process.
>
> --- In vantage@yahoogroups.com, "mmcwilliams22" <mmcwilliams22@> wrote:
> >
> > In the client config you can change the SelectTextOnEnter Value to True
> >
> > <SelectTextOnEnter value="True" bool="" />
> >
> > --- In vantage@yahoogroups.com, "jgiese1988" <jgiese@> wrote:
> > >
> > > I am having issues with users missing the extra 0 in these fields. Is there a way that when you click into a number field that the field clears or all of the text highlights that you can easily enter information in without always removing the leading 0 before the decimal?
> > >
> >
>
2
I am having issues with users missing the extra 0 in these fields. Is there a way that when you click into a number field that the field clears or all of the text highlights that you can easily enter information in without always removing the leading 0 before the decimal?
3
In the client config you can change the SelectTextOnEnter Value to True

<SelectTextOnEnter value="True" bool="" />

--- In vantage@yahoogroups.com, "jgiese1988" <jgiese@...> wrote:
>
> I am having issues with users missing the extra 0 in these fields. Is there a way that when you click into a number field that the field clears or all of the text highlights that you can easily enter information in without always removing the leading 0 before the decimal?
>
4
Wow duh of course why did I look there... For global config changes like that can I just unzip the clientrelease zip on the server make the change and rezip it, that way when people get it installed it has those changes right away? How can we push that to clients with it already installed or is this a manual process.

--- In vantage@yahoogroups.com, "mmcwilliams22" <mmcwilliams22@...> wrote:
>
> In the client config you can change the SelectTextOnEnter Value to True
>
> <SelectTextOnEnter value="True" bool="" />
>
> --- In vantage@yahoogroups.com, "jgiese1988" <jgiese@> wrote:
> >
> > I am having issues with users missing the extra 0 in these fields. Is there a way that when you click into a number field that the field clears or all of the text highlights that you can easily enter information in without always removing the leading 0 before the decimal?
> >
>
5
I heard something at the Vantage Midwest User's group that you can say your client is new version...For example, we have 8.03.409C - could change to 8.03.409C2? Try it in your test environment first...

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jgiese1988
Sent: Monday, September 12, 2011 9:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: number fields



Wow duh of course why did I look there... For global config changes like that can I just unzip the clientrelease zip on the server make the change and rezip it, that way when people get it installed it has those changes right away? How can we push that to clients with it already installed or is this a manual process.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "mmcwilliams22" <mmcwilliams22@...> wrote:
>
> In the client config you can change the SelectTextOnEnter Value to True
>
> <SelectTextOnEnter value="True" bool="" />
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "jgiese1988" <jgiese@> wrote:
> >
> > I am having issues with users missing the extra 0 in these fields. Is there a way that when you click into a number field that the field clears or all of the text highlights that you can easily enter information in without always removing the leading 0 before the decimal?
> >
>



[Non-text portions of this message have been removed]