It doesn’t close (I just tried your exact code to make sure). However, whenever you click the Run button Panorama automatically brings the frontmost data window from that database to the front, either a form or the data sheet. Depending on the size and position of that data window, it may cover the procedure window. In that case it looks like it disappeared, but it’s really still open if you move the frontmost window out of the way. This is the way all procedures work, not just the particular code you have submitted here.
No, that is absolutely ok. But the chevrons are necessary if the variable name contains anything other than
- plain letters A thru Z (upper or lower case).
- underscores (_)
- numbers (but not allowed as the first character)
Only plain letters can be used without chevrons. Letters with any kind of accent marks or diacriticals require the chevrons, as do any ligatures, like
This actually has nothing to do with how Apple’s text editor code decides what a word boundary is – that is an entirely separate issue.
I agree with this – I generally try to avoid the use of chevrons as much as possible. Keep in mind that in Panorama X the field name can be different than the field title that is shown in the data sheet. So you could name the field SvaermtrangName for use in formulas, but still display the field title as SværmtrangName. Best of both worlds, I think.