Field Order Problem

[trudnoz]

When I modify a program on my XP PRO home computer and change fields the field order follows the field order I have programmed. However at work where I am networked and FoxPro 2.6 resides on the server (Windows 2000 server) the field order does not change when I change the program. Any idea of how to fix this. The workstations are also XP Pro

Thanks

Zev

 

[cricket]

Are you referring to the order in which fields display in a BROWSE window?

 

[trudnoz]

Yes, sorry I dabble trying to keep my application working. It is the order you see on the screen view. I modify the SPR file and don't modify the SCX file. So I guess it is on the screen appearance. I'm not that concerned about the order in the browse window. What I do is the first field to be entered is "Enter Last Name". After I enter the last name the next field to highlight is the "Locate" button to look-up a patient. The problem happened when I added a field get m.firstname. At home the progression is lastname, firstname, and then locate button. While at the office it still goes to locate after I have put in the lastname. It does not go to m.firstname. Both lastname and firstname are get variable statements.

Thanks

Zev

 

[JRB-Bldr]

The BROWSE window most often uses the LAST format which was used. The parameters (field order, window size, etc.) are saved in the FOXUSER.DBF table.

Unfortunately despite the actual field sequence of a table, the settings of the BROWSE window itself can determine the field display order.

I am guessing that the BROWSE window was created/opened at some time with a different field order (possibly the default field order) at work than was opened at your home.

The safest and most certain way to get a standardized field order displayed is to intentionally establish that order with your own command.

USE MyTable IN 0
SELECT MyTable
BROWSE FIELD Field1, Field2, Field3, Field4 ... etc.

Good Luck,
JRB-Bldr

 

[TamarGranor]

First, it's not a good idea to modify the SPR rather than the SCX. It's a dead end that leads to having to maintain the code by hand instead of with a useful tool.

As for your specific problem, it sounds like you inserted the the new @GET in a different place in the two copies of the form. The tab order is the order that you issue the @GETs.

Tamar