A5 renaming objects

[Leo Cohen]

Sporadically A5 renames an object in the control Panel, where it is known as Namer, to Namer0 when I run it. It also happens with functions. For example, I have a function, insert_name() that has been renamed insert_name0() so far as the Debugger is concerned. If I change insert_name() the change does not appear in insert_name0() and the wrong function gets executed!!!

The only way I can can rid of insert_name0() is to close A5 and restart it.

[Selwyn Rabins]

RE: A5 renaming objects

a5 does this for a very good reason.

say you have a form called 'myForm'.

when you open this form a5 creates a 'form object' in memory. all objects have names. for convenience, a5 assigns an object name that is the same as the form name (as long as the resulting name is a legal object name, and is not a duplicate object name).

legal object names cannot have spaces, or start with certain characters.

also, and obviously, objects must be uniquely named.

so, after you open the first instance of 'myForm' there will be an object in memory called 'myForm'.

now, if you open a second instance of this form, a5 must come up with a unique object name, hence 'myForm0'.

[Leo Cohen]

RE: A5 renaming objects

Thanks, Selwyn. My problem is that short of closing and restaarting A5 I can't get form0 out of the memory. Is there a simpler way to do it?

Leo.

[Edward Larrabee]

RE: A5 renaming objects

You can use A5.FORM_ENUM() and then close any forms that should not be open.

The an important question is why you have multiple copies of the same form open in the first place.

If you are referring to the form in the context of one of its scripts, this is when you use the TOPPARENT and PARENTFORM aliases.

[Leo Cohen]

RE: A5 renaming objects

In a very simple test DB with just 1 table and 2 forms, I have only opened one of them for design, Membership. After running and returning Membership to design a few times, I close Membership and try to open the table for field rules. But A5 says that a form is open that uses the table.

So I run A5.form_enum(2) in the interactive window and A5 tells me I have two forms. Only Membership has been opened, so I execute

:membership.close(.f.) and get the message "Argument is incorrect data type".

From the earlier posts, Membership apparently persists in memory. And the above steps aren't getting rid of it.

[CALocklin]

RE: A5 renaming objects

Are you ever opening Membership as dialog form? If so, it must be explicitly closed in your script even after you click something to "close" it - as in, make the form disappear from the screen. That's the only common thing I can think of that leaves forms hanging around.

Why are you putting .F. in the close command? Just use:
membership.close() (or Membership0.close() as appropriate)
That's probably why you are getting "Argument is incorrect data type".

Cal Locklin
www.aimsdc.net

[Leo Cohen]

RE: A5 renaming objects

I only open Membership as modal. It is closed with an Exit button on running, and in the current situation has been closed in design. In fact, there are no forms or tables open when I try to open the table for Membership in Field Rules mode.

I used close(.f.) because that's the way it appears in A5 examples and in the code generated by the Close Action; this may be a case of error-by-example.

[Marcel Kollenaar]

Sporadically A5 renames an object in the control Panel, where it is known as Namer, to Namer0 when I run it. It also happens with functions. For example, I have a function, insert_name() that has been renamed insert_name0() so far as the Debugger is concerned. If I change insert_name() the change does not appear in insert_name0() and the wrong function gets executed!!!

The only way I can can rid of insert_name0() is to close A5 and restart it.

Leo,

I had the same experience. This is what I did.

1. I started a db.
2. chose a form.
3. clicked the design button
4. changed an action script
5. saved the script
6. clicked the view button again on the forms tab <<<<----
7. pushed some buttons but they didn't work

I saw later that there was still a form in editing while I was viewing the 'same' form.

Obviously it is possible to start the same form (with old information) but with another unique object name (as Selwyn explains).

In step 6 when I use the edit/view button on the control panel bar (not the control panel form) I still keep on working/viewing on the same form object.

What is the purpose that you can start viewing a form that actually is in edit mode.

It's rather confusing.

Regards,

Marcel

[Tim Kiebert]

I have found that as an inexperienced designer that while designing I often muck things up and end up with tables left open that can't be seen. Then you can't get into field rules etc as described in previous posts. I have found a handy little function called a5_forceclosetables(). I have assigned this to a button on the a5 system toolbar for Control Panel.

When tables don't close properly just push the button and 90 percent of the time it fixes it. Only occasionaly when I really stuff up do ineed to close A5 altogether.