Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Complex Design Problem
Message
 
 
To
07/05/2009 14:58:57
General information
Forum:
ASP.NET
Category:
ADO.NET
Environment versions
Environment:
C# 3.0
OS:
Windows XP
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01398420
Message ID:
01398440
Views:
53
>The order of the fields in the table doesn't matter.
>
>BTW, I prefer to put the PK/FK notation at the start of the field name (ex.: PKOrder, FKOrder). I find them easier to spot this way.
>

Too late :) I already re-designed, re-configured TAs and build both DataSets and BL projects. Now the fun begins working with UI and BL.


>>While I was doing it, I also figured that I named my FK incorrectly (it was originally named OrderPK instead of OrderFk). In order to rename I had to add this column at the end of the other fields. Would it matter if the fields in TA are not in the exact order as in the table in the SQL Server or I better delete this field in TA and re-add both of them in the right new order?
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform