hi all,
I have to convert an existing app from eVB to VB.net and I'm asking:
what i have to do with the DB?
i know that the "pocket access + ADOCE" solution is no longer
supported (well, i don't want to use InTheHand because i'm looking for
a free solution)...
does this mean that i have necessarily to use SQL server CE?
isn't there a lighter solution?
i read on some group that "One possible replacement for Pocket Access
would be the DataSet object in ADO.NET"... what does it mean? Do i
have to create a local XML database?
any help or suggestions?

another topic: form navigation
i read an article where MS suggest to use a form caching system and a
form call stack... does anybody use this system? is it really useful
to increase application performance?
or do you use the old eVB trick with 1 real form = N frames as logical
forms?

thank you
matteo gabella

Re: DB to use instead of pocket access + forms navigation by Ginny

Ginny
Wed May 12 09:30:05 CDT 2004

Matteo,

You could certainly create an XML "database" and use it easily with a
DataSet, but I would only recommend this approach if your data volume will
be small - maybe only a few K. For a similar but faster solution, consider
using the CSV data adapater on www.opennetcf.org. And of course SqlCe is a
great choice for large amounts of data.
--
Ginny Caughey
.Net Compact Framework MVP

"Matteo Gabella" <gabu2000@tin.it> wrote in message
news:bda2e795.0405120537.2b041373@posting.google.com...
> hi all,
> I have to convert an existing app from eVB to VB.net and I'm asking:
> what i have to do with the DB?
> i know that the "pocket access + ADOCE" solution is no longer
> supported (well, i don't want to use InTheHand because i'm looking for
> a free solution)...
> does this mean that i have necessarily to use SQL server CE?
> isn't there a lighter solution?
> i read on some group that "One possible replacement for Pocket Access
> would be the DataSet object in ADO.NET"... what does it mean? Do i
> have to create a local XML database?
> any help or suggestions?
>
> another topic: form navigation
> i read an article where MS suggest to use a form caching system and a
> form call stack... does anybody use this system? is it really useful
> to increase application performance?
> or do you use the old eVB trick with 1 real form = N frames as logical
> forms?
>
> thank you
> matteo gabella