>Hi All,
>
>We're developing a C# winforms application that talks to a MS SQL Server database. A requirement was made to have the application run "offline" (disconnected I suppose is another way to describe it?). We were able to make a fully functioning offline version using XML files for the offline data storage mechanism. This worked very well for a small database. Unfortunately, it chugged very slowly (almost unusable) for much larger data.
>
>So my question is, what alternatives do we have to try to solve this speed issue? I've already thought of the obvious one (keep the offline data to an "acceptable minimum") but I'm looking for other ways :) We've been considering MSDE, however, the issue of synchronizing the offline data with the online/live SQL Server database remains. Is it "automagic"? What if the database was ORACLE instead? Does MSDE play fair with ORACLE?
>
>TIA for any suggestions and/or comments.

Mike,
Depending on release date planned you might either use MSDE or SSE as the local data store (or some other engine like VFP,MDB...).
SQL server, MSDE/SSE merge/replication is best to take offline and then synch IMHO. Creating a VFP database, adding it view(s) and then taking the view(s) offline is another way.
If, saying much larger data, you mean a database that's over 2Gb then MSDE is out. SSE limit is 4Gb AFAIK.
Whatever way you go I suggest use PKs that are 'for replication' and that typically is a GUID on all backends.
Cetin