>what CASE tool is that? The ones I've seen want to fully migrate the key (same name both tables). Some even make it difficult to do anything else.
xCase. I think there's an internal setting that allows you to specify your preference, but I dismember.
>
>>One last habit I've adopted is to put the columns in alphabetical order. Helps to find columns in large tables easier, and since we use Hungarian notation, all like-type columns are grouped together (which makes it easy to double-check defaults, null acceptance, and so forth.
>
>hmm - I've learned not to count on order in the physical table other than having keys up top. What order I have is more based on logical groupings of the fiels - i.e. Name, address, city, state, zip together
This is like the Hungarian notation thing...more of an issue for a development shop. Plus, it's a case of "my data model...my rules". I don't want to waste time trying to understand someone else's logic for grouping columns, which tends to fall to pieces if new fields need to be added. Just my preference.
>
>Thanks for your input - I'm interested in your case tool answer.
>
>thanks,
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.