I have four layouts named: WhiteForm, BlueForm, PinkForm, PeachForm

The layouts are in the above order. How can I create a script that
will go to the next layout in the above order with just one button.
So, if the current layout is PinkForm, the script/button when
activated, will switch to the PeachForm layout.

Thanks!

cheshirekat
About to have some cinnamon swirl ice cream - hope it's good. Should
have gotten the B&J Cherry Garcia.

"cheshirekat" <cheshirekat@pobox.com> wrote in message
news:e694f236.0310130105.6067f854@posting.google.com...
> I have four layouts named: WhiteForm, BlueForm, PinkForm, PeachForm
>
> The layouts are in the above order. How can I create a script that
> will go to the next layout in the above order with just one button.
> So, if the current layout is PinkForm, the script/button when
> activated, will switch to the PeachForm layout.
>
> Thanks!
>
> cheshirekat
> About to have some cinnamon swirl ice cream - hope it's good. Should
> have gotten the B&J Cherry Garcia.

Where do you want to go from PeachForm?  I'll assume back to WhiteForm.

There are two ways to accomplish this.  The first way is very simple.

Set Field [Global Number, If (Status (CurrentLayoutNumber) = 4, 1, Status
(CurrentLayoutNumber) + 1)]
Go To Layout [layout number from field value "Global Number"]

Substitute the appropriate numbers in the If statement above to make this
work for your database (the "4" refers to the Layout Number for PeachForm,
the first "1" refers to the Layout Number for WhiteForm).

If this doesn't work for you, we can look at the solution that requires the
LayoutNames design function.

cheshirekat@pobox.com (cheshirekat) wrote in message news:<e694f236.0310130105.6067f854@posting.google.com>...
> I have four layouts named: WhiteForm, BlueForm, PinkForm, PeachForm
> 
> The layouts are in the above order. How can I create a script that
> will go to the next layout in the above order with just one button.
> So, if the current layout is PinkForm, the script/button when
> activated, will switch to the PeachForm layout.
> 

Well. Now that I've already given my email address to the spam bots
since newsgroups through my ISP has been down ... sigh

What I did with the above query is nested ifs. If layoutname is
Blueform, go to layout PinkForm ... etc.

However, my reason for asking the group is that I've got it stuck in
my head that there's another way of doing it. I don't know why I think
so - is there?

cheshirekat
now expecting another spam-flooded email address

In article <e694f236.0310130844.3f234bac@posting.google.com>,
cheshirekat@pobox.com (cheshirekat) wrote:

>cheshirekat@pobox.com (cheshirekat) wrote in message
news:<e694f236.0310130105.6067f854@posting.google.com>...
>> I have four layouts named: WhiteForm, BlueForm, PinkForm, PeachForm
>> 
>> The layouts are in the above order. How can I create a script that
>> will go to the next layout in the above order with just one button.
>> So, if the current layout is PinkForm, the script/button when
>> activated, will switch to the PeachForm layout.
>> 
>
>Well. Now that I've already given my email address to the spam bots
>since newsgroups through my ISP has been down ... sigh
>
>What I did with the above query is nested ifs. If layoutname is
>Blueform, go to layout PinkForm ... etc.
>
>However, my reason for asking the group is that I've got it stuck in
>my head that there's another way of doing it. I don't know why I think
>so - is there?
>
>cheshirekat
>now expecting another spam-flooded email address

There is almost always another way of doing it ;)

Somebody previously suggested that you should use layout number instead of
layout name in your script.  The advantage to that would be that if you
decide later to change the proper sequence of forms, all you have to do is
change their oder in Layout Mode, rather than going in and changing each
line of the script.

An advantage to your approach is that it is conceptually very simple.

An even more simple approach (conceptually) might be to have a unique
button for each layout.  Each button would have a simple command (not even
a script) telling it to go to the appropriate layout.

-- 
 

cheshirekat wrote:
> Well. Now that I've already given my email address to the spam bots
> since newsgroups through my ISP has been down ... sigh

Why don't you put a spamblock, like I do, I put INVALID right after the @. It 
does work for me. I put the INVALID after the @, as it messes up spambots 
collecting my domain name as well.
-- 
"When the darkness comes, those who once lived in the shadows will need to guide 
the lost ones."
    -till next time, Jameson Stalanthas Yu -x- <<poetry.dolphins-cove.com>>
     consul@INVALIDdolphins-cove.com ((remove the INVALID to email))

In article <bmhs5v$fij$1@usc.edu>,
 ~consul <consul@INVALIDdolphins-cove.com> wrote:

> cheshirekat wrote:
> > Well. Now that I've already given my email address to the spam bots
> > since newsgroups through my ISP has been down ... sigh
> 
> Why don't you put a spamblock, like I do, I put INVALID right after the @. It 
> does work for me. I put the INVALID after the @, as it messes up spambots 
> collecting my domain name as well.

As you can see, I normally do change my email address. But, as I was posting 
from googlegroups (or wherever in the heck I was) I didn't know how to 
change my email address, though I did look. Probably something I overlooked 
since I usually only lurk from google.

cest la vie (or something like that)

In article <greg-1310031032280001@ava35.drizzle.com>,
 greg@demREMOVEberdatabase.calm (Greg Dember ) wrote:

> In article <e694f236.0310130844.3f234bac@posting.google.com>,
> cheshirekat@pobox.com (cheshirekat) wrote:
> 
> >cheshirekat@pobox.com (cheshirekat) wrote in message
> news:<e694f236.0310130105.6067f854@posting.google.com>...
> >> I have four layouts named: WhiteForm, BlueForm, PinkForm, PeachForm
> >> 
> >> The layouts are in the above order. How can I create a script that
> >> will go to the next layout in the above order with just one button.
> >> So, if the current layout is PinkForm, the script/button when
> >> activated, will switch to the PeachForm layout.
> >> 
> >
> >Well. Now that I've already given my email address to the spam bots
> >since newsgroups through my ISP has been down ... sigh
> >
> >What I did with the above query is nested ifs. If layoutname is
> >Blueform, go to layout PinkForm ... etc.
> >
> >However, my reason for asking the group is that I've got it stuck in
> >my head that there's another way of doing it. I don't know why I think
> >so - is there?
> >
> >cheshirekat
> >now expecting another spam-flooded email address
> 
> There is almost always another way of doing it ;)
> 
> Somebody previously suggested that you should use layout number instead of
> layout name in your script.  The advantage to that would be that if you
> decide later to change the proper sequence of forms, all you have to do is
> change their oder in Layout Mode, rather than going in and changing each
> line of the script.
> 
> An advantage to your approach is that it is conceptually very simple.
> 
> An even more simple approach (conceptually) might be to have a unique
> button for each layout.  Each button would have a simple command (not even
> a script) telling it to go to the appropriate layout.

Conceptually simple - that's me. :-)

Ok. I guess I overlooked the part in the documentation where it clarifies 
what the layout number is for each layout. Is the layout number derived from 
the creation order of the layout, or are we talking about a layout number 
that is akin to a unique ID? If it's not a unique ID, what happens when I 
delete a layout - is a number missing? Hmm. Maybe the layout number is 
simply the numerical assignment by their position in the layout order? So 
that will always match the number of layouts in the order arranged?

But, to throw in something else for consideration. I have the buttons to 
access those four layouts. I have additional layouts at the end that I 
consider "hidden" because of their infrequent use. I guess that's one of the 
reasons I wanted to reference the layouts by name. By using a button to 
cycle forward (another cycles backward) through the main layouts, it saves 
me screen clutter. I hate clutter. By not including the less necessary 
layouts, then I'm assuming this would be more efficient as far as the time 
it takes to click and sift through to the correct layout.

Before you ask, I do have buttons for each individual layout - to go 
directly to a specific layout. But, I also know that I can remember a 
keyboard shortcut much more easily then the exact layout button. Therefore, 
the cycle button is generally for when I'm "browsing" data - not entering. I 
wanted to tie the button in to the same script/keyboard command for 
consistency. I think it's easier to click one button (or shortcut) until I 
get the right layout then to flail about from button to button in those 
moments I'm unsure of what I want until it's "seen".

OK. That was probably TMI - but at work, our Access "database specialist" 
kept saying that there was no way to switch from one screen or another 
without using buttons. For data entry that sucks, because one wants to keep 
their hands on the keyboard as much as possible instead of reaching for the 
mouse. When I'm browsing, efficiency isn't as important, so I keep my hand 
on the mouse. We fought a lot about the fact that data entry of a three page 
document shouldn't include reaching for the mouse 17 times (no lie, I 
counted) because one loses momentum and it's just inefficient when the data 
entry person already has to search through a stack of documents to dig out 
those three documents. Since I argued so strongly about this with a person 
that "was always right", I look for ways to ensure I don't create the same 
traps in my own databases.

Oops. Time to go to the dentist. I've been busy with my databases all night 
and haven't slept a wink. I'm hoping I'll be able to eat a big bowl of ice 
cream later (we each have our own rewards), so he better be gentle. :-)

>
>Ok. I guess I overlooked the part in the documentation where it clarifies 
>what the layout number is for each layout. Is the layout number derived from 
>the creation order of the layout, or are we talking about a layout number 
>that is akin to a unique ID? If it's not a unique ID, what happens when I 
>delete a layout - is a number missing? Hmm. Maybe the layout number is 
>simply the numerical assignment by their position in the layout order? So 
>that will always match the number of layouts in the order arranged?
>
>But, to throw in something else for consideration. I have the buttons to 
>access those four layouts. I have additional layouts at the end that I 
>consider "hidden" because of their infrequent use. I guess that's one of the 
>reasons I wanted to reference the layouts by name. By using a button to 
>cycle forward (another cycles backward) through the main layouts, it saves 
>me screen clutter. I hate clutter. By not including the less necessary 
>layouts, then I'm assuming this would be more efficient as far as the time 
>it takes to click and sift through to the correct layout.
>
>Before you ask, I do have buttons for each individual layout - to go 
>directly to a specific layout. But, I also know that I can remember a 
>keyboard shortcut much more easily then the exact layout button. Therefore, 
>the cycle button is generally for when I'm "browsing" data - not entering. I 
>wanted to tie the button in to the same script/keyboard command for 
>consistency. I think it's easier to click one button (or shortcut) until I 
>get the right layout then to flail about from button to button in those 
>moments I'm unsure of what I want until it's "seen".
>
Layout # is indeed the order of the layout in the list.  Given what you've
now explained, here's what I would do:

Make your four main layouts be the first four in the layout order.  Make
four scripts (and put them as the first four in the script order).  Make
each script a one-liner that sends you to the layout with the same #. 
Then make a fifth script that cycles through your layouts the way (I
think) Glenn described several posts back.  

Now, just using keyboard shortcuts, you can either click directly to the
proper layout if you know what it is (using 1,2,3, or 4)   OR you can use
5 to cycle through without thinking if that's what you prefer at a given
time.

-- 
 

In article <greg-1610030751110001@ava13.drizzle.com>,
 greg@demREMOVEberdatabase.calm (Greg Dember ) wrote:

> >
> >Ok. I guess I overlooked the part in the documentation where it clarifies 
> >what the layout number is for each layout. Is the layout number derived from 
> >the creation order of the layout, or are we talking about a layout number 
> >that is akin to a unique ID? If it's not a unique ID, what happens when I 
> >delete a layout - is a number missing? Hmm. Maybe the layout number is 
> >simply the numerical assignment by their position in the layout order? So 
> >that will always match the number of layouts in the order arranged?
> >
> >But, to throw in something else for consideration. I have the buttons to 
> >access those four layouts. I have additional layouts at the end that I 
> >consider "hidden" because of their infrequent use. I guess that's one of the 
> >reasons I wanted to reference the layouts by name. By using a button to 
> >cycle forward (another cycles backward) through the main layouts, it saves 
> >me screen clutter. I hate clutter. By not including the less necessary 
> >layouts, then I'm assuming this would be more efficient as far as the time 
> >it takes to click and sift through to the correct layout.
> >
> >Before you ask, I do have buttons for each individual layout - to go 
> >directly to a specific layout. But, I also know that I can remember a 
> >keyboard shortcut much more easily then the exact layout button. Therefore, 
> >the cycle button is generally for when I'm "browsing" data - not entering. I 
> >wanted to tie the button in to the same script/keyboard command for 
> >consistency. I think it's easier to click one button (or shortcut) until I 
> >get the right layout then to flail about from button to button in those 
> >moments I'm unsure of what I want until it's "seen".
> >
> Layout # is indeed the order of the layout in the list.  Given what you've
> now explained, here's what I would do:
> 
> Make your four main layouts be the first four in the layout order.  Make
> four scripts (and put them as the first four in the script order).  Make
> each script a one-liner that sends you to the layout with the same #. 
> Then make a fifth script that cycles through your layouts the way (I
> think) Glenn described several posts back.  
> 
> Now, just using keyboard shortcuts, you can either click directly to the
> proper layout if you know what it is (using 1,2,3, or 4)   OR you can use
> 5 to cycle through without thinking if that's what you prefer at a given
> time.

Good.  Now I know my thinking wasn't  too far off from what other people 
were suggesting. I do have the four main layouts listed first. Four buttons 
I can do as I already have the cycle button. 

I had root canal done at the dentist this morning. Didn't get a wink of 
sleep last night. Spent all afternoon and all night buying a refurb PC, 
setting up PC, trying to get an extra, yet nearly dead monitor to work on 
the PC, then finally just using my good 17" on the PC because I also hadn't 
eaten all day and it was very late. After the monitor glitch - all was 
smooth sailing with the new PC and printing and making sure it would run at 
least one new game. And to think, my little home network didn't fall apart. 
I'm still flabbergasted that the hubby finally tired of his circa Flinstone 
75Mhz laptop in favor of something nearly current with a bit of speed.

Tis a bummer that my FileMaker Pro5 is a Mac only CD. I bought the 6 
edu/student version and would give him the old version if it was a 
dual-platform CD. I really want to exchange FM files because I know I can 
count on him to brag to his friends about the custom databases he's been 
wanting. I'd also like to work on his XP machine when I create some 
databases to learn the differences since I haven't gotten to work on any PCs 
that used FMP - just had to refuse the hubby on his old relic machine. I've 
got to make more time to look through the FMPro books I have, but I'm too 
exhausted to get too swept up in the possibilites.

Hmm. Maybe I should go make sure FMP 5 isn't a dual OS CD before I go to 
sleep. I think I need a snack first. I jabber too much when I'm sleepy.

Thanks everyone for the insight!