M
Matteo Gabella
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
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