By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,717 Members | 2,069 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,717 IT Pros & Developers. It's quick & easy.

An "offline" dotnet component to an asp.net web app

P: n/a
I have an asp.net web application that I use with an Access data backend. I
want to add a mini-client "offline" DotNet Windows App component in the
event that I don't have an internet connection or maybe for some other
reason.

I envision downloading the data from the online version as needed (say using
a web service) and loading that into the client version.

How should I go about this? Should I store the data as XML and use that as a
database for the client app? I don't want to use Access for the client app
if I don't have to, as the client might not have Access. This begs the
question that if the client has the .Net framework will it have MDAC in
which case I might be able to use Jet independent from Access. But let's
just say it doesn't have MDAC.

Can I use XML as a database? The amount of data I have is small, under 1000
records right now but it might increase to a few thousand over a period of
time. I am the only user of this tool.

Any advice is appreciated.
Aug 8 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.