Just my 2 cents worth. And of course a request for more.

I really hate change. Some would call me a stick in the mud, others call me consistent. But I have been learning thanks to the Lantica team that sometimes changes can be good.

I have really become very fond of the control panels in Sdesigner. When I started playing with Sesame I thought why do I need the property viewer, I wondered why could they not just display the existing values on the property editor. Now I love being able to view my element property values in one box and just click on the appropriate feature in the editor box. They obviously thought this through and I am glad they did. I have been realizing that if I give up thinking the way I was used to (The Q&A way) I can achieve amazing things with Sesame.

Just goes to show, us old dogs can learn new tricks.

Another really great feature I have come to love is the ability to export all my program layouts to a file. If I notate each piece of code properly, not only do I have good documentation of what I have done it also acts as a programmers notebook of how to accomplish specific tasks in the future.

So in a nutshell I am trying to say to anybody out here struggling with changing to Sesame, Hang in there, the end of the trip looks promising and to the Lantica team I am saying GREAT JOB and THANKS.

As always the more that is given to me the more I want. (Is this just a man thing? ??? ) Is there a way to print or export all my field element Names and the associated values? I have been attempting to maintain this data in a Spreadsheet and it is prone to errors.

I agree with Bob's comments but in database I would like the option to be able to close the Tree Command Menu like the favorites list in IE.
This old dawg still likes to be able to have full screen view

Now for my Question 

I have a record entry form which includes elements "City, State, Zip, +4, Add2" etc.
Sdesigner rename the label "+4" to  LE6
In the programing of LE6, I have a navigation statement on element exit of "Goto Add2". This statement does not excute but it did test OK under programing.
If I place the same statement under the element "Zip" then it excutes correctly.

I presume this has something to do with the label name or the change thereof, can somebody shed some light on this simple statement, thnx

Quote:


Becky,

I have a command button at the top of my form  labeled open/close if the tree is open when it is selected the tree will close. If the tree is closed it will open.

Just make a command button and attach this code. It works well.


// Opens or closes command Tree dependent on the state it is currently in

var state as Int 
   
state = @CloseCommandArea() // Returns the current Command Tree state
if state = 0 then
     CloseCommandArea(1)  // Closes the Command Tree
else
     CloseCommandArea(0)  // Opens the Command Tree

Hope this helps.

Quote:


Ah, if only I could get the folks in Lantica marketing to ask for features so nicely!

Unfortunately, the decision isn't really up to me (alone). You should send an email to support@lantica.com. They can make sure it gets discussed as a new feature and put on the list.

Quote:


Becky the "field" that you had named as " +4 " contained an invalid character - the " + " sign.  That is why Sesame renamed this (L)ayout (E)lement as LE6 .  I can't explain why the programming isn't working, unless somehow in the changing of the name, Sesame is not tracking the change properly, or you have to make a manual correction somewhere.  Hopefully someone that understands Sesame better than I do can answer this for you!

TJ, I agree, don't know why this simple statement is not working, so I deleted the element "+4" changed the navigation in "Zip" to "Goto Add2" and it excutes fine just like before. I then replaced the element and named  it "Zip4" adjusted the navigation to refleck the "Goto Add2" and it doesn't  work again.
Its always the nickel and dime things that give ya the headache 

Bob,
Just wondering, do you work in a think tank by any chance? 
I haven't looked at the use of "Visibility, @Visibility" as yet, must admitt I had skimed right over that one, your idea makes for good thought but then I look at the process of the total issue and then think I have to do all that to every form I create! Just to get full screen
I say in the words of John Stossel "give me a break"
lets keep it simple and add a "command tree close" to the upper menubar and be done.

So I guess I will plead my case to support@Lantica and keep my fingers crossed.

Quote:


Since you did ask so nicely - its been implemented. The close command tree and open command tree items have been added to the "View" menu. They are disabled if an SBasic program invokes either CloseCommandArea or OpenCommandArea, or if Sesame is started using the "-closed" flag. It will be in the next release.

To the Lantica/Sesame Team, I and the others that are not so sharp in programing thankyou for implementing this request for an idiot button   It will surely make life easier for me.

Thankyou, Thankyou, Thankyou  
and yes Bob that really is Customer Support, to Xkaes I hope you have been reading this thread, if you jump ship now look at all the great support, comradely not to mention a great Data Base Program you will be missing, but if you do I've got  a copy of Access lying around in a draw somewhere that I will sell ya cheap.
Enough said  

Erika
Ok heres the lay out, the only programming is in the Open/Close button, thanks to Bob. The Date field has a standard @date program; everything else is stripped clean except for the navigation statements.
When the form was created the order of entry went Date, Invoice #, Name, Ship To.
But I wanted it to go Date, Invoice #, Name, Address, City, State, Zip, Zip4, Ship To, Terms and so on.

In programming on element exit I placed the Goto next element, starting with Name thru to Zip4, but when leaving Zip4 it goes to Terms instead of Ship To. Now if I place the Goto Ship To in the Zip element the order of execution works.
I have also set the program execution order to match what I want but that doesn't work either, I know I have to be missing something simple
Also note some of the elements names have changed from previous post, I was thinking that the names might have been the issue.

Maybe the screen shot will stay there now

Tried again but for some reason I cannot get the image to remain viewable in the post.
any ideas why?

Erika, I will do as you suggest, then recheck it for the 10th  time, I know its going to be one of those duh! moments  

Quote:


Becky, I am not sure if I understood the problem correctly, but I think, this might be related to placements of horizontally placed elements on the form. If it is not, please excuse me.

Natural Navigation (Navigation without any goto statement) is based on layout element Y position. If you put multiple elements horizontally, and Y position of those elements are not the same, you will find that natural navigation would not work the way you hoped it would. Just use <tab> keys in search mode to see that naviagion work properly, especially in the elements placed horizontally.

If not, check Y position of each element individually that are placed horizontally and make sure y position of all horizonally placed elements are the same (by looking in the property viewer) and change them if you have to by moving the elements as needed.

One can do that by choosing the elements in one line, and  aligning vetrically (top) using property editor.

Becky,

In order for the screenshot to be visible on this Forum, the image must be available online somewhere. You can't embed a graphic into the post. The image file needs to be accessible, the same way it needs to be accessible to be seen on a web page.

As to your navigation issues, can you send a copy of your application to support@lantica.com ? You can remove the records if you need to. It will be easier to help you if I can actually see what we've got.

Becky,

Your invoice looks nice! 

Quote:

Becky,

The problem is likely to be the GoTo's, not the other programming. There may be two GoTo's interfering with each other.

Becky, throwing some ideas at you... maybe something will help...

Remember that programming should reference LAYOUT ELEMENT NAMES, not field names in the database.  Check to be sure that the LE name for ZIP4 is really set to the proper thing, and that what is on the screen is not what you might be using in programming, if the actual layout element name is different.  (Hope that makes some sense.)

Navigation can be affected by read-only fields, and element level security.  Don't know if this can have any effect on what you are doing.

Is the "Ship To" layout element named properly?  Is there any chance it is named slightly differently?  (Maybe an extra space, or no space)

Try building another totally new (start from scratch) database, that contains only a few fields.  These would be layout elements:  State, Zip, Zip4, Ship To, and Terms.  These are the layout elements that are the ones that might be involved.  I included State only because it is a non-necessary field, to sort of get things going but not be a critical field.  Create these new LE in a vertical fashion in a new database.  Add the GoTo statements as you have in the other database.   See if you can get proper navigation.  (skipping from Zip to Ship To, etc.)  Once that is working, then we know there is not some anomoly with a LE named Zip4.   

Now move the Ship To  layout element around on the screen, positioning it differently to see if position on the screen has any effect.  It shouldn't.

Some of my ideas may be totally out in left field - but I thought I'd offer them.   Good Luck!

Becky,

I found the problem and it is a bug regarding Combo Boxes. A fix will appear in the forthcoming release. As a temporary workaround, simply move the Combo Box "Terms" so that it, and no other combo box is the "natural" next L.E. after Zip4.

Thank you for your patience!