enter vs. update mode

[William Perry]

I have a script that I would like to run on a particular table's "can_save" event when the user is entering a new record, but I want to skip it when the user is updating an existing record. Is there a way to capture whether the table is in "enter" or "update" mode and then use an if mode = "enter" end if type of decision. Any help is appreciated. Thanks,

-Bill

[Stan Mathews]

RE: enter vs. update mode

.file_mode_get()
Syntax:
Mode = .file_mode_get()
Description:
Returns the mode in which the table referenced by was opened.
Possible values for Mode are: 16 (Read only, exclusive), 18 (Read/write,
exclusive), 64 (Read only, shared) and 66 (Read/write, shared).

[Stan Mathews]

RE: enter vs. update mode

Sorry, ignore the other. This is the mode method you need.

.mode_get()
Syntax:
Data Entry Mode = .mode_get()
Description:
Returns a number that indicates the current Data Entry Mode for the table
pointed to by the table pointer ().
The possible return values are:
Return Value Data Entry Mode
0 No data entry is currently taking place.
1 A Change operation is underway.
2 An Enter operation is underway.
Example:
'This script can be attached to an OK button on a dialog
'to make sure the current records is saved before the
'dialog is closed.
'------------------------------------------------------
tbl = table.current()
IF tbl.mode_get() > 0 THEN
parent.commit()
END IF
parent.close()

[William Perry]

RE: enter vs. update mode

Stan: Thanks for the reply. If I understand correctly I could use the following to run my script for new entries and not run it for updates of existing records:

tbl = table.current()
if tbl.mode_get() = 2 THEN

RUN THE SCRIPT THAT YOU WANT TO RUN FOR NEW ENTRIES

end if
end

I'm going to give it a try. Thanks again

-Bill

[William Perry]

RE: enter vs. update mode

Stan: I tried what you suggested and it worked perfectly. I knew that there must be a way to capture the mode, but wasn't sure where to look for info on syntax, etc. I just filled out the A5 survey and praised the message board. This is exactly what I was talking about - this board is quite unique. Thanks again

-Bill

[Stan Mathews]

RE: enter vs. update mode

Did you install the online documentation?

I know it can be quite obtuse at times. You almost have to know the answer before you can find the proper reference.

If you have the online documentation, there are a few tricks you can use when searching to limit the "hits" to pertinent passages.

When I searched for the syntax you needed I searched for "mode_" (knowing I was looking for a "method"). This eliminates finding the word "mode" references. You could also search for get(), put(), etc. with the same effect.
You don't want to see "plain" instances of get or put.

[William Perry]

RE: enter vs. update mode

Stan: I thought that I had installed everything from my initial A5 disc (help, books, etc.), but maybe I missed something. You mentioned that you searched for "mode_", but where did you search for that. When I go to the help pull down and search "mode_" in the index tab, I don't get anything. Did I miss some resourse that I should have installed? Thanks.

-Bill

[Stan Mathews]

RE: enter vs. update mode

From the Windows Start Menu, Programs, Alpha software, The first item should be a folder "Books". In that folder should be, after three others, XBASIC REFERENCE MANUAL.

[William Perry]

RE: enter vs. update mode

Stan: Thanks again. I've got it, I was just looking in the wrong place. I had been going to the "help" pull down once A5 was running, which provides some very good help and an index, but not this info. I look forward to some interesting reading.

-Bill