From: liz@paradoxcommunity.com   
      
   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:   
   > 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   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)