wow!! good explanation. In Visual Studio 2010, there is an option to avoid explicitly recreating the tables when there is a change in the schema. This is by going to Tools>>Options>>Database Tools>>Table and Database Designers>>
uncheck the option 'Prevent saving changes that require table recreation' . Thanks
@varunrpillai I you table is full of data and you decide to do this your data may be deleted! Thats why it is important to spend long time designing a table
hello dbasoftsolutions -you mentioned that when you had a problem adding a field to registration it didn't permit you to add, and the solution is create an sql script that you will run and will recreate all the fields, indexes and relationship again. What if you already save data / record in the tables, does it return or save the data/records also back to those tables?
wow!! good explanation. In Visual Studio 2010, there is an option to avoid explicitly recreating the tables when there is a change in the schema. This is by going to Tools>>Options>>Database Tools>>Table and Database Designers>>
uncheck the option 'Prevent saving changes that require table recreation' . Thanks
varunrpillai 11 months ago
@varunrpillai I you table is full of data and you decide to do this your data may be deleted! Thats why it is important to spend long time designing a table
aquadog90 3 weeks ago in playlist More videos from dbasoftsolutions
Good explanation!
SeeKerSoulNamah 1 year ago
hello dbasoftsolutions -you mentioned that when you had a problem adding a field to registration it didn't permit you to add, and the solution is create an sql script that you will run and will recreate all the fields, indexes and relationship again. What if you already save data / record in the tables, does it return or save the data/records also back to those tables?
JMemini8 1 year ago