Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-10-29 : 08:24:31
|
| Rick writes "We have an ASP.NET application which uses a full SQL Server database. We want to add the capability for salespeople to install (in a separate procedure) our app locally on a tablet PC with a blank MSDE database. We'll figure out the mechanics for this part.Then, periodically, when they are able to access our'master' ASP.NET app from the road, we would like for them to be able to selectively download rows from a number of tables from the central SQL db to their local MSDE. They will make changes locally, then later on upload it back to the central db.I am thinking that creating a linked server temporarily on the master db (via a stored proc. call to sp_addlinkedserver) to transfer this data back and forth to the MSDE db may work, but haven't found any specific info/case studies/etc. that supportsthat. In addition, I have created an MSDE database on our tablet PC and haven't found a way to successfully 'broadcast' its presence to the SQL db server so that I can attempt to create a linked-server definition to it.Do you have any thoughts as to how to make this approach work, or any ideas as to a better way to solve our problem?Thanks very much for your help!" |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2004-10-29 : 12:35:19
|
| You might want to look into serialized DataSets / DataTables on the client side. Do some searching on MSDN about disconnected clients.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
|
|
|
Is Linked Server/MSDE solution the best way to go for this problem?