Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Complex Design Problem
Message
 
 
To
07/05/2009 14:34:34
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:
01398436
Views:
50
>You will need to add the new field in the DS, in your T-SQL commands and (of course) your code.
>

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?

Thanks.



>>I was thinking about it couple of days ago (or may be even weeks - lost count), but when I discussed this problem with my boss then, I think the answer was to not keep it there.
>>
>>At the end of the day the orders are going to be added to the main database, so having price field in the OrderDetails is not mandatory.
>>
>>However, it does present a complexity in the design, DS,TA, BL, so I guess I rather go ahead with the simpliest solution and add price into the OrderDetails.
>>
>>Now, would my TA refresh or I would need to somehow change several methods?
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform