Exiting A Record

[LaRetta]

Hi

I was reading an interesting post and wanted the opinion of all you wise FM'ers. A new record isn't really *created* until a field is exited, right? This post was a discussion between Andy Gaunt and WhiskeyWolf on FM Cafe' and they mentioned two options when scripting: 1) Exit Record Request at the beginning of the script and 2) "go to field "cursor." I searched on Forum and couldn't find a relevant post.

The similarity is obvious but I think it's important to understand the differences. FM (non-HELP) says: Exit Record Request puts the cursor not in a field, Go To Field puts the cursor in another field, and Go To Field "cursor" isn't listed.

This is something I most certainly will need to utilize. I would appreciate a clearer perspective than FM help gives.

Would you use Exit Record Request or Go To Field "Cursor" to place the cursor outside of any field and why?

LaRetta

[jasonwood]

The Exit Record/Request script step is the same as using the "Go to Field" script step without specifying any field. This commits the field data, just like clicking outside of a field.

I'm not sure about what is meant by "cursor" in the example you found...

[LaRetta]

Hi Jason!

The Exit Record/Request script step is the same as using the "Go to Field" script step without specifying any field.

Yes, I guess my point is that they appear the same; however, things aren't always what they seem (although in this case, they may be).

I guess my question was more from a resource usage standpoint or whether they behave differently in different situations, x-plat differences, vers-compatibility issues, any funky problems with either, etc.

As for the "Cursor", it appears that the cursor can be *identified* just as a field can? I want to take this off my list of things to learn, so I appreciate your input!

LaRetta

[BobWeaver]

I think "Cursor" must have been an error, or else it is the actual name of a field that someone was referring to.

[LaRetta]

Oh Hi Bob

I just re-read the post, I guess they created a field called cursor. Emmm, sorry ... now that makes more sense. I didn't know which would be the best function to use

Well, I don't think I want to create a field just to Go To Field Cursor, so I'll use Exit Record Request!! It's my blooper night, can't you tell?

LaRetta

[CobaltSky]

Hmmn... I know the post you are referring to, and yes, the suggestion offered was to create a redundant field called 'cursor' to place the cursor in.

The principle behind this proposed work-around is, presumably, that if the cursor field doesn't appear on any layouts, a Go to Field ["Cursor"] step will fail, and in failing, will remove the cursor from the record, thus exiting the record.

The problem is that this was not explained in the post. Nor was it explained why you would need such a work-around in the first place, since the 'Exit Record/Request' script step has been around since 1995 (it was introduced with version 3) - and in any case, prior to 1995, simply leaving the Go to Field[ ] parameter empty - which has the same effect - was a the widely used alternative technique.

Notwithstanding the above, since the Exit Record/Request step exists, one might as well use it (why go 'round the block to visit your neighbour?!) - and as it has no parameters, it is conceivable that it uses a processor cycle or two less (if that were an issue), since it doesn't have to interpret before it can act.

[LaRetta]

Hi Ray

Thanks for the explanation. No, I certainly don't want unnecessary fields ... or calcs ... or anything else that isn't necessary, for that matter! Although a bit embarrasing, I would rather ask than make wrong assumptions. Thanks much!

LaRetta