>I have just had an odd circumstance that required an unexpected work-around with the Data Environment.
>
>I should first mention that I have been modifying my structures do deal with new requirements.
>
>I had 2 tables in the data environment that were related. I disconnected the relation before I modified the structure because the primary field for the relation was being effected.
>
>After I finished with my structures, I reindexed and packed the files and then hooked up the relation again in the Data Environment. I then found that the relation would no longer work. I checked the relation with a simple browse command and confirmed the relation was no longer holding.
>
>After a lot of fooling around, I disconnected the relation in the DE and went into the Before Open Tables Event and wrote the relation in there and now everything is fine.
>
>This is now scaring me about the stability of the DE. Has anyone else come across this before and is there something I should do differently to make the DE work properly?
>
>Mike Smith
Perhaps you should consider opening tables in the Form.Load() event, instead.
Commands would typically include USE, SET ORDER, CursorSetProp("Buffering"), SET RELATION.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)