I have built an application that requires me to modify one or two table
structures once or twice a year. These tables are attached to a form. In all
cases, I am adding to the table structure with additional alpha field types.
My problems is that when the original form is opened, the fields have
shifted is some cases. Example: field027 configured on the orginal form will
now change to a random field say field30a. So when I look at the original
form several of the fields have changed locations. Is there a way to lock
these field positions on a form so they are always referencing to the
original field name? I hope this makes sense!

Thanks
Dan

Your writing makes sense, but the situation you describe doesn't. :-)
At least not in my experience.


Do you not use 'real' names for the fields in the table?

I've NEVER had a field change on a form, when I only add fields to the end
of the table and when I don't otherwise change field names.

Are you doing this interactively, or in code?

------------------------------
Tony McGuire

I am adding fields to the table structure. I don't change the field names,
only add new ones. Usually they are not at the end of the table. I change
the structure via Paradox table design, not code.


"Tony McGuire" <png.paradoxcommunity@com> wrote

Well, add only to the end and I would bet the issue goes away.

I asked about naming since your post talked about field027 and field30a.

Do you not give them meaningfull names?


--
------------------------------
Tony McGuire

If you add fields in places other than the end of the table, you could
be creating problems. At the very least, after this, you should run
table repair (not check, repair).

If you open the form in design mode and then restructure your table, it
may prevent the problem.

Better to just put new fields at the end - it's not like the position
matters - you can even save tableview properties with fields in the
position you prefer if you're using tableviews.

Liz


Dan wrote:

The names used are desc027 and desc030a. They are meaningful on a spec form
that I am using. The tables are used for multiple spec forms and each field
may have a different set of data depending on the key field form number
referenced.

Dan

"Tony McGuire" <png.paradoxcommunity@com> wrote

Liz,

This is great! I took your advice did a table repair and all of the field
references came back to the correct reference location on my form. It also
worked if I just did a table restructure. It is important that I keep the
field names in the table structure in order.

Thanks again.

Dan


"Liz McGuire" <liz (AT) paradoxcommunity (DOT) com> wrote

IMO, that's an illusion, but if you're gonna do it, run table repair
after every restructure.

Liz


Dan wrote:

Having a structure where you often have to change it by adding fields
usually indicates a normalization problem. It certainly is, at very
least unusual and abnormal. In adddition, your response to Liz about
needing to keep fields in a specific order further suggests you
misunderstand table structure, schema and normalization. PERHAPS there
is a good reason. I can't imagine one. Check out my Database Basics and
Normalization papers at our paradox resources pages (link in my
signature) for more info on this.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982