Help with Design

[faaslave]

That is what I thought. If I see it again in forum, I will let you know.

When I am making a script, I can't figure out how to switch between windows.

Also, if you want to make the new window a certain size, it asks for a name of the window. That doesn't make sense to me.

What I would like to do is as follows:

Make a new window, go to layout blah blah, resize to fit, put the window over here in a specific place.

or

Make a new window, go to layout, tile vertically, resize to fit, go back to original layout, resize this one to fit, then back to the new window.

I guess what I am saying is I want a new window, I don't want it on top of the old one, I want the original shape of the orignal window, I want the correct shape of the new window, and I want them tiled. That way, when a user opens a help screen, they can still see the window they are reading about. And I hate when the tile feature changes the shape to fill the screen.

As I said in the beginning, it looks like there is a feature to tell FM exactly where to put a window, but it wants a new name for the window. Why doesn't it just want the name of the layout?

Very confusing, but I am feeling good because I am getting close to this thing being done.

Thanks alot,

Dave

[-Queue-]

You could have the same layout used for different windows, such as one in form view and one in list view. So the window name is crucial to operations. If you are using layout names for your window names, then you will use the same name when referring to a window. You may want to test that there isn't already a window open that contains the same name.

If [not Position(

[faaslave]

when my windows open they just use the name of the file, then as more windows open it will add a -1, -2, etc. I have not named any windows up to this point. I just let FM do it

So lets see if I get this. I could name a window upperrightcorner. And make it so that it will be in the upper right corner of the screen, at a set size, etc., then in a script say, open new window, specify (upperrightcorner), then go to layout whatever, and presto, the window is just where I want it? That would be great......

Dave

[faaslave]

Forget the last post.

I figured it out, and it works great.

My only complaint is that I can't find a way to have a window in layout mode tell you what the pixel dimensions of the layout. So you just have to play around till it works. Not a big deal. I will upload the latest soon, for anyone who is interested. I am getting closer

Dave

[faaslave]

Well, here is a look at the latest.

When I am in the Client/Invoice layout, I have a portal that shows all of the clients invoices. On each one you have the ability to pull up that invoice with a click. It comes up in a new window using the invoice lookup script. I tried to perform a find so that when that window shows up, it has the record you want, and the rest of that clients invoices so you can scroll through them.

I can't seem to get it to work. It has all invoices.

When performing a find, how do I say, give me this record and all other records by this client? I know that I will need to show the staus area, if I can get this to work.

Thanks

Dave

[-Queue-]

When you Specify your GTRR step, select 'Show only related records'. Since your relationship is based on client id, only records for that client will be found.

[faaslave]

Wow, that was easy.

Thanks again, did you get a chance to see some of the improvements?

Dave

[faaslave]

Another question,

I have a field called taxable that has a checkbox, either it is checked or not

I have another field called category. This uses a value list, Pick either Product or Service

So what I was thinking is why not have the taxable field be a calculation, If the user selects Product as the category of the item, it is taxable, and if they select Service, it should stay unchecked.

I tried to make the Taxable field a calc, and use the Case calc Case(Category="Product";1;0)

This didn't work. I figured 1 would return true and 0 false, but I don't think I am going about this the right way since that just returns a number

Thanks

Clueless Dave

[-Queue-]

Category = "Product" should work. The 1 and 0 are redundant. Make Taxable a number field and use a value list of 1 for it. When you want to test it, use Case( Taxable ... ) for true (1) or Case( not Taxable ... ) for false (0).

[faaslave]

Thanks,

I made taxable a number field and used a calc, Case(Category="Product";1;0)

Then I made a field that displays on the layout a calc field, Case(Taxable="1";"Yes";"No")

That works. I think you were trying to show me a way to do it with one field, but I didn't understand. If this is what you meant then, I got it.

But as far as I can tell, this works.

Dave

[-Queue-]

I meant that the Case test for your taxable calc is redundant. Category = "Product" is all you need. If it's true, it will return a 1; if false, zero.

You don't need an extra field to display. You can put Taxable on the layout and format it as a boolean. With the field selected, go to Format -> Number and select 'Format as Boolean'.

When you want to test Taxable for other calcs, you don't need the = "1" part, since a zero is false and a one is true. You only need Case( Taxable; result1; result2 ).

[faaslave]

Sorry I have not been on in awhile. I wasn't ignoring your response. I have been in LAS at a convention, and trying not to lose money.

Thank you very much

Dave

[Ender]

Hmm, I wonder what the record is for posts in a single thread.

[-Queue-]

I don't know. But I'd rather not try to break it.