Click here to Skip to main content
15,892,746 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hello people!

I have trouble with our newly configured application. This application is connected to a SQL server 2005, and runs custom C# code. I have written it to use datasets and bound object at the user end, and Microsoft sync framework with bidirectional sync to the server.

My challenge, which i have tried googling, is that occasionally a new row is not given a CreationDate at the SQL server table, and therefore is not synced throughout the users. It has the auto-generated triggers on the table, from set-up off local-database cache in the program.

My question is, can I remove this trigger, and instead make sure that CreationDate is inserted by the application on the client side?
If not, how can I work at this problem?

And why is the date stamp in format UTC date? I see benefits from showing the user the LastEditDate, but then I need the correct time for my time zone.
Posted
Updated 11-Oct-11 9:23am
v2

1 solution

For trigger removal see DROP TRIGGER[^].
 
Share this answer
 
Comments
MrDeej 11-Oct-11 15:30pm    
I think you can also right-click the trigger on the table, and select delete, from Visual Studio

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900