Use of Tab Key causes unwanted insert of record.

[Fred Zag]

I have a data entry form which is opened for insert. I would like the user to be able to use the tab key to navigate from field to field, possibly even looping through the same fields numerous times, and then deciding when to save the record by choosing a "Save Button". But Alpha automatically saves the record and begins to insert a new record after looping through the fields. If I navigate from field to field with the mouse I can accomplish the desired result, but it would be much easier for the user if I could use the tab key.

[Stan Mathews]

Contiunous enters

I have a data entry form which is opened for insert. I would like the user to be able to use the tab key to navigate from field to field, possibly even looping through the same fields numerous times, and then deciding when to save the record by choosing a "Save Button". But Alpha automatically saves the record and begins to insert a new record after looping through the fields. If I navigate from field to field with the mouse I can accomplish the desired result, but it would be much easier for the user if I could use the tab key.

Your form probably does not have "continuous enters" restricted.

Setting User Restrictions

When creating a form, you can set restriction on what users can do. For example, you can allow users to enter new records, but disallow them from changing existing ones. By restricting command access, you can prevent unauthorized users from damaging data and inexperienced users from becoming confused by unnecessary choices.

Choose Form > Properties and display the Form tab.

Place a check to the left of each restriction you want to enforce. The following table provides a description of the restrictions.

Restriction
Description

Enter Record
Prevents new record entry.

Change Record
Records cannot be changed.

Delete Record
Records cannot be deleted.

Find Commands
Users cannot access the Find-by-Key command.

Query Commands
Users cannot access Query commands.

Select Index
Prevents primary index/query changes.

Select Range
Users cannot set ranges.

Navigate
Prevents users from moving to a different record.

Open/Edit Layout
Prevents users from entering Edit Mode when opening a different layout.

Continuous Enters
When the user finishes entering a new record, a new record is not automatically created.
Browse Mode
Users cannot switch to Browse Mode.

And there is some additional information here.

[Fred Zag]

Thanks Stan.

Don't know how many times I've scrolled past that parameter and I guess it just never sank in. I have to look at another app, I think I must have used it before. In any event I'm sure that's it. But meanwhile I've made so many changes to the form that I created some other problems. Well, I'll get it cleaned up and confirm back here later, but I'm quite certain that is what I was (blindly) looking for.

Thanks again,

[Fred Zag]

And again, thanks Stan.

Works like a charm. Also went back and found that antiquated app and, sure enough it worked way back then too. Ahh, the impending Alzheimers makes the Phorum even more valuable!

And thanks again for the speedy response.

[CALocklin]

I think all the features available in these later versions probably even makes the youngsters feel like they're getting Alzheimers. Either that or they just haven't figured out how much they don't know yet.

A5v1 was a lot more complicated than A4 (the DOS version) but there were sure a lot fewer commands to remember back then and we didn't have to worry about HTML, FTP, CSS, ODBC, ADO and all the rest of that stuff.

[Fred Zag]

You're certainly right there Cal. I don't go quite that far back - never did work with v4. But today's myriad of options certainly has me scratching my head a lot of the time. (And there's not that much up there left to scratch!)

I seem to remember the neat new stuff once I've worked with it but it evidently replaces some of the old functions I haven't used in a while. When I spent a greater portion of my working time with Alpha it was a lot easier, but now too many other "responsibilities" are vying for what little memory is left. :)

[masteralone]

Hiya Cal, Fred,

I used to frequent the A4 and early A5 boards. I remember Cal helping me on several occasions.

I have worked with A4 and with all but A5 v4.5 and v5 (skipped them) and agree with Cal that v1 was easier in some ways than the latest versions because the commands and functions built into it were far less than now and fewer parameters to them.

Lol, guess the thing I miss the most is being able to have set level field rules like we had in A4 that over rode .dbf (table) field rules but allowed us to have dbf field rules that we usually set the same as the set rules in case we had to work in the .dbf (table) by itself and not part of the set. Sometimes, the .dbf was used in different sets and often, the .dbf field rules were all that you needed instead of set field rules. What I find very inconvenient and time consuming is creating xbasic scripts that do the same as the old A4 set field rules.

Guess you have heard or said that yourself Cal.

Thanks for letting me put my two cents worth in before Alzhiemers gets me too.

Oran