Re: Changing table structure and losing a forms field position and reference


only add new ones. Usually they are not at the end of the table. I change
the structure via Paradox table design, not code.

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


.

Relevant Pages

  • Re: object_* and instance_* methods
    ... from this naming scheme. ... that's the smell of good design to me. ... categories, rocks are rocks, trees are trees, and birds are birds. ... when those categories get sorted into hierarchies differences emerge. ...
    (comp.lang.ruby)
  • Re: Poll: How Many Delphi Users Did or Did Not Learn Pascal At University?
    ... my dad helped to design the Burroughs machines back in the 60s and ... a cheap boss that I learned to program. ... than how we were using the RBase system, so I brought both the manuals ... Paradox appeared to me to be the best ...
    (borland.public.delphi.non-technical)
  • Re: Paradox Tables...
    ... Since it appears you need to have Paradox tables, ... I need to modify the design of some tables originally Paradox tables, ... OK, but it's not, because primaries keys has disappeared, is there anyway ...
    (microsoft.public.access.externaldata)