>My boss (also a good friend of mine so I can speak freely to him) believes it is not a good idea to use the foxpro database designer to create links and referential integrity constraints on tables. He says that it is more trouble than it's worth. He would rather use the tables the way they were used in Foxpro 2.6, all free tables. He also think it is better to code the referential integrity in the application.
>
>My feeling is that he is mistaken. What is the general opinion on the issue? Do the VFP programmers use the database designer? What are the advantages and/or inconvenients that I might be missing?


Hey Eric,
When it's VFP data: use a one-field surrogate Primary key and consider filling it with a GUID. The data designer & RI builder will then become good friends. What specific troubles have/has you/he had?

Good luck, Steven-