I have seen SQL Server tables with 20+ fields of varchar 4000. Total
lack of discipline and perfect example of laziness that is infecting the
software world's concept of "data." Needless to say, the shoddy approach
of that application also showed through into the UI and other areas.
In terms of VFP tables, I have to say I've never come close to the 65k
limit. And though I don't claim to be an expert at normalization, I just
seem to never enjoy creating those 200 field tables that have stuff like
month1, month2, month3, month4.... yada yada. That's probably because I
have a different kind of laziness - once I design a system I NEVER want
to go back and change code. If a software change is required for any
other reason than a new requirement surfaced, it means I failed in my
design.
-Charlie
On 11/2/2020 7:25 PM, MB Software Solutions, LLC wrote:
I've got a client who's main data table for their orders is over 2300
wide for record length.
Anybody seen any wider in their travels?
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/fc440527-7584-a697-2f6e-662ae6822...@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
