How can I read/write Access 2003 file in Windows Mobile v5.0 ?

  • Thread starter Thread starter Chris
  • Start date Start date
Ginny, this just let us to read and write on an Access database
indirectly. But what if there is a Access database created by an eVB
application that we need to read from a .NETcf application?

In this case the MDB file is not on a desktop PC but in the handheld it
self, so I believe ADS is not helpfull here.

Victor Espina
 
You can't open Access (mdb) files on the device. There is an obsolete
database format called Pocket Access (cdb) for Pocket PC, there isn't a way
to use this directly from .NETCF, you would need a wrapper around the ADOCE
control. Ideally you need to move away from using Pocket Access, to SQL
CE/Mobile or a third-party supported engine.
Details on the wrapper for legacy support only here:-
http://community.inthehand.com/forums/2110/ShowThread.aspx#2110

Peter
 
Ginny,
I'm just installed VS.Net 2005, so I need to find and install the SQL Server
Everywhere ?
And import Access MDB to SQL SE and export to PDA use (what extension name
that I don't know) ?
And therefor I can use your method to access my database file ?

Thanks,

Chris
 
Peter,

The only way you mention it is pay more for buy new ADOCE from inthehand.com
?


Chris
 
Exactly... amazing, uh?

I'm having the exact same problem than you have, and as far I had read
in Internet, MS doesn't offer ANY way to access a MDB in a PDA device.

The only way I have found to access an MDB file in a PDA device is
buying some commercial ADOCE wrapper.

I hope you have more luck than me... if you find any free solution,
please let me know.

Regards,

Victor Espina
 
Yep, that's true. The last version of the software that they had was a
while back. They *did* make a significant effort to let everyone know that
support for ADOCE was going away long before it was dropped. This, of
course, favors their own newer database products, which you might find
ominous, but, if it's really valuable to have that capability, it seems to
me that the cost of a commercial wrapper should be worth it to have support.

Paul T.
 
Should they have maintaine 16-bit Windows 3.1 driver and software support
too? At some point the cost of maintaining backward compatibility outweighs
the benefits. CDB format isn't even supported on new devices, so why spend
time and money adding support for something that won't have devices that
will even run it? The CDB fomat had a lot of inherent problems and needed
to be scrapped. If you have resonably well abstracted code, replacing it
shouldn't be terribly painful.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
 
I suppose that the word "better" is the reason. The main reason, best I can
tell, that VFP still exists is that there is a large and *very* vocal
community of FoxPro MVPs which constantly are pounding the Microsoft product
team to keep it around one more version (they are rabid, maybe literally
;-). MS has announced several times that VFP was going away only to be
pounded back into one more version at the MVP Summit, from what I've heard.
I seriously doubt that MS is making any money on VFP, but sometimes a vocal
minority can be more effective than a silent majority. ADOCE didn't have
that.

You have to obsolete old products or, over time, you're going to die as a
company. You try to pick those technologies, libraries, tools, etc. which
have the least impact on the users or which allow you to make the biggest
jumps in performance, usability, or reliability. It's just a fact of life.

Paul T.
 
Yes. MDB comes up periodically as a desirable format and I can certainly
understand that. The alternative that MS would express, I think, would be
using remote data access or synchronization via something like SQL Server on
the desktop and the matching code on the device, rather than moving all of
the data to the device all the time.

Hey, I could show you what can be done in C++, too! :-) Everyone has their
own favorites, usually based on their experience with a given environment.
In any case, I'm a device OEM, so not really a suitable convert!

Paul T.

Victor Espina said:
I agree with both of you. The point is that MDB files are NOT obsolete... I
have Access 2003 installed in my PC and i'm pretty sure that is not the
lastest version...

Anyway, I guess that your are right. In my particular case, the problem is
that I'm programming a new applicacion en C# and NETcf for a client that
used eVB for its PDA applications. They have some key data in a CDB file
that I should read from my .NET apps... and I had to tell him that I can't
do that from C#... of course, I can spend the extra bucks and buy this
ADOce wrappers, but that will cost me money and of course I don't like
that particulary.

Regards,

Victor Espina

P.D.: and for VFP... yes, you maybe right.. but you can be 100% sure that
if I could have the chance to sit with you and show you what can be done
in VFP, you will realize why VFP comunity keeps making presure to force MS
to not only continue devoloping VFP but to market it in a more aggresive
way.

The last time I did this "sitting" thing was with a project leader that
was suppossed to train me in a the language they had picked for that
particular project... Delhpi or something like that, I don't remember
now... one of the project team had seen a presentation I made some months
ago about some apps I've been devoloping for another company and he
insists to the project leader to ask me to make the same presentation to
him... all this toke place at first hour in the morning of the first
training day.. by noon, the project leader was calling to its supervisor
to CONVINCE HIM why they should use VFP and recode all what was being done
so far!!


I suppose that the word "better" is the reason. The main reason, best I
can tell, that VFP still exists is that there is a large and *very* vocal
community of FoxPro MVPs which constantly are pounding the Microsoft
product team to keep it around one more version (they are rabid, maybe
literally ;-). MS has announced several times that VFP was going away
only to be pounded back into one more version at the MVP Summit, from
what I've heard. I seriously doubt that MS is making any money on VFP,
but sometimes a vocal minority can be more effective than a silent
majority. ADOCE didn't have that.

You have to obsolete old products or, over time, you're going to die as a
company. You try to pick those technologies, libraries, tools, etc.
which have the least impact on the users or which allow you to make the
biggest jumps in performance, usability, or reliability. It's just a
fact of life.

Paul T.

Victor Espina said:
Paul, I think the point is:

Why you (M$) make so big efforts so sell me your new technologies and
convince me to invest time and money creating an application based on
that techology, just to let me down in a couple of year because you just
has invented a new and better technology?

I've been a VFP programmer for years, even before MS buyed out Fox
Company... and I STILL can access data created in 1990!!

If at some time M$ sell us out that you can create and use MDB files in
PDA devices (with eVB for example) they should give us a way to continue
accesing those files with their new technologies.

IMHO

Victor Espina


Paul G. Tobey [eMVP] wrote:
Yep, that's true. The last version of the software that they had was a
while back. They *did* make a significant effort to let everyone know
that support for ADOCE was going away long before it was dropped.
This, of course, favors their own newer database products, which you
might find ominous, but, if it's really valuable to have that
capability, it seems to me that the cost of a commercial wrapper should
be worth it to have support.

Paul T.

Exactly... amazing, uh?

I'm having the exact same problem than you have, and as far I had read
in Internet, MS doesn't offer ANY way to access a MDB in a PDA device.

The only way I have found to access an MDB file in a PDA device is
buying some commercial ADOCE wrapper.

I hope you have more luck than me... if you find any free solution,
please let me know.

Regards,

Victor Espina


Chris wrote:
Ginny,
I'm just installed VS.Net 2005, so I need to find and install the SQL
Server Everywhere ?
And import Access MDB to SQL SE and export to PDA use (what extension
name that I don't know) ?
And therefor I can use your method to access my database file ?

Thanks,

Chris


"Ginny Caughey [MVP]" <[email protected]>
¼¶¼g©ó¶l¥ó·s»D:[email protected]...
Chris,

You might want to try the Access Database Synchronizer for SQL
Everywhere: http://blogs.msdn.com/sqlservereverywhere/

--
Ginny Caughey
Device Application Development MVP


Hello all,

I know we can convert mdb to cdb, but how can I access the .cdb
files in
vs.net 2005 CF ?

someone can provide sample code or else ?

by the way, The files ADOCE.Net in InTheHand Software
(www.inthehand.com)
is removed. (That in the following link)
http://msdn2.microsoft.com/en-US/library/ms837914.aspx


thanks all !


Chris
Click to expand...
Click to expand...
Click to expand...
 
Yes, MDBs are not, but CDBs are. And I agee that there's no decent solution
for an Access desktop DB to device sync (though the CDB wasn't very good to
begin with).


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--


Victor Espina said:
I agree with both of you. The point is that MDB files are NOT obsolete... I
have Access 2003 installed in my PC and i'm pretty sure that is not the
lastest version...

Anyway, I guess that your are right. In my particular case, the problem is
that I'm programming a new applicacion en C# and NETcf for a client that
used eVB for its PDA applications. They have some key data in a CDB file
that I should read from my .NET apps... and I had to tell him that I can't
do that from C#... of course, I can spend the extra bucks and buy this
ADOce wrappers, but that will cost me money and of course I don't like
that particulary.

Regards,

Victor Espina

P.D.: and for VFP... yes, you maybe right.. but you can be 100% sure that
if I could have the chance to sit with you and show you what can be done
in VFP, you will realize why VFP comunity keeps making presure to force MS
to not only continue devoloping VFP but to market it in a more aggresive
way.

The last time I did this "sitting" thing was with a project leader that
was suppossed to train me in a the language they had picked for that
particular project... Delhpi or something like that, I don't remember
now... one of the project team had seen a presentation I made some months
ago about some apps I've been devoloping for another company and he
insists to the project leader to ask me to make the same presentation to
him... all this toke place at first hour in the morning of the first
training day.. by noon, the project leader was calling to its supervisor
to CONVINCE HIM why they should use VFP and recode all what was being done
so far!!


I suppose that the word "better" is the reason. The main reason, best I
can tell, that VFP still exists is that there is a large and *very* vocal
community of FoxPro MVPs which constantly are pounding the Microsoft
product team to keep it around one more version (they are rabid, maybe
literally ;-). MS has announced several times that VFP was going away
only to be pounded back into one more version at the MVP Summit, from
what I've heard. I seriously doubt that MS is making any money on VFP,
but sometimes a vocal minority can be more effective than a silent
majority. ADOCE didn't have that.

You have to obsolete old products or, over time, you're going to die as a
company. You try to pick those technologies, libraries, tools, etc.
which have the least impact on the users or which allow you to make the
biggest jumps in performance, usability, or reliability. It's just a
fact of life.

Paul T.

Victor Espina said:
Paul, I think the point is:

Why you (M$) make so big efforts so sell me your new technologies and
convince me to invest time and money creating an application based on
that techology, just to let me down in a couple of year because you just
has invented a new and better technology?

I've been a VFP programmer for years, even before MS buyed out Fox
Company... and I STILL can access data created in 1990!!

If at some time M$ sell us out that you can create and use MDB files in
PDA devices (with eVB for example) they should give us a way to continue
accesing those files with their new technologies.

IMHO

Victor Espina


Paul G. Tobey [eMVP] wrote:
Yep, that's true. The last version of the software that they had was a
while back. They *did* make a significant effort to let everyone know
that support for ADOCE was going away long before it was dropped.
This, of course, favors their own newer database products, which you
might find ominous, but, if it's really valuable to have that
capability, it seems to me that the cost of a commercial wrapper should
be worth it to have support.

Paul T.

Exactly... amazing, uh?

I'm having the exact same problem than you have, and as far I had read
in Internet, MS doesn't offer ANY way to access a MDB in a PDA device.

The only way I have found to access an MDB file in a PDA device is
buying some commercial ADOCE wrapper.

I hope you have more luck than me... if you find any free solution,
please let me know.

Regards,

Victor Espina


Chris wrote:
Ginny,
I'm just installed VS.Net 2005, so I need to find and install the SQL
Server Everywhere ?
And import Access MDB to SQL SE and export to PDA use (what extension
name that I don't know) ?
And therefor I can use your method to access my database file ?

Thanks,

Chris


"Ginny Caughey [MVP]" <[email protected]>
¼¶¼g©ó¶l¥ó·s»D:[email protected]...
Chris,

You might want to try the Access Database Synchronizer for SQL
Everywhere: http://blogs.msdn.com/sqlservereverywhere/

--
Ginny Caughey
Device Application Development MVP


Hello all,

I know we can convert mdb to cdb, but how can I access the .cdb
files in
vs.net 2005 CF ?

someone can provide sample code or else ?

by the way, The files ADOCE.Net in InTheHand Software
(www.inthehand.com)
is removed. (That in the following link)
http://msdn2.microsoft.com/en-US/library/ms837914.aspx


thanks all !


Chris
Click to expand...
Click to expand...
Click to expand...
 
Paul, I think the point is:

Why you (M$) make so big efforts so sell me your new technologies and
convince me to invest time and money creating an application based on
that techology, just to let me down in a couple of year because you just
has invented a new and better technology?

I've been a VFP programmer for years, even before MS buyed out Fox
Company... and I STILL can access data created in 1990!!

If at some time M$ sell us out that you can create and use MDB files in
PDA devices (with eVB for example) they should give us a way to continue
accesing those files with their new technologies.

IMHO

Victor Espina
 
I agree with both of you. The point is that MDB files are NOT
obsolete... I have Access 2003 installed in my PC and i'm pretty sure
that is not the lastest version...

Anyway, I guess that your are right. In my particular case, the problem
is that I'm programming a new applicacion en C# and NETcf for a client
that used eVB for its PDA applications. They have some key data in a CDB
file that I should read from my .NET apps... and I had to tell him that
I can't do that from C#... of course, I can spend the extra bucks and
buy this ADOce wrappers, but that will cost me money and of course I
don't like that particulary.

Regards,

Victor Espina

P.D.: and for VFP... yes, you maybe right.. but you can be 100% sure
that if I could have the chance to sit with you and show you what can be
done in VFP, you will realize why VFP comunity keeps making presure to
force MS to not only continue devoloping VFP but to market it in a more
aggresive way.

The last time I did this "sitting" thing was with a project leader that
was suppossed to train me in a the language they had picked for that
particular project... Delhpi or something like that, I don't remember
now... one of the project team had seen a presentation I made some
months ago about some apps I've been devoloping for another company and
he insists to the project leader to ask me to make the same presentation
to him... all this toke place at first hour in the morning of the first
training day.. by noon, the project leader was calling to its supervisor
to CONVINCE HIM why they should use VFP and recode all what was being
done so far!!
 
Ja Ja. Let be peace!!

I'm a MIS programmer, so C++ is too much "lowlevel" for what I need.
But I give you that C (C, C++, C#, Obj-C) is indeed a beautifull and
powerfull language.



Victor Espina

Yes. MDB comes up periodically as a desirable format and I can certainly
understand that. The alternative that MS would express, I think, would be
using remote data access or synchronization via something like SQL Server on
the desktop and the matching code on the device, rather than moving all of
the data to the device all the time.

Hey, I could show you what can be done in C++, too! :-) Everyone has their
own favorites, usually based on their experience with a given environment.
In any case, I'm a device OEM, so not really a suitable convert!

Paul T.

Victor Espina said:
I agree with both of you. The point is that MDB files are NOT obsolete... I
have Access 2003 installed in my PC and i'm pretty sure that is not the
lastest version...

Anyway, I guess that your are right. In my particular case, the problem is
that I'm programming a new applicacion en C# and NETcf for a client that
used eVB for its PDA applications. They have some key data in a CDB file
that I should read from my .NET apps... and I had to tell him that I can't
do that from C#... of course, I can spend the extra bucks and buy this
ADOce wrappers, but that will cost me money and of course I don't like
that particulary.

Regards,

Victor Espina

P.D.: and for VFP... yes, you maybe right.. but you can be 100% sure that
if I could have the chance to sit with you and show you what can be done
in VFP, you will realize why VFP comunity keeps making presure to force MS
to not only continue devoloping VFP but to market it in a more aggresive
way.

The last time I did this "sitting" thing was with a project leader that
was suppossed to train me in a the language they had picked for that
particular project... Delhpi or something like that, I don't remember
now... one of the project team had seen a presentation I made some months
ago about some apps I've been devoloping for another company and he
insists to the project leader to ask me to make the same presentation to
him... all this toke place at first hour in the morning of the first
training day.. by noon, the project leader was calling to its supervisor
to CONVINCE HIM why they should use VFP and recode all what was being done
so far!!


I suppose that the word "better" is the reason. The main reason, best I
can tell, that VFP still exists is that there is a large and *very* vocal
community of FoxPro MVPs which constantly are pounding the Microsoft
product team to keep it around one more version (they are rabid, maybe
literally ;-). MS has announced several times that VFP was going away
only to be pounded back into one more version at the MVP Summit, from
what I've heard. I seriously doubt that MS is making any money on VFP,
but sometimes a vocal minority can be more effective than a silent
majority. ADOCE didn't have that.

You have to obsolete old products or, over time, you're going to die as a
company. You try to pick those technologies, libraries, tools, etc.
which have the least impact on the users or which allow you to make the
biggest jumps in performance, usability, or reliability. It's just a
fact of life.

Paul T.

Paul, I think the point is:

Why you (M$) make so big efforts so sell me your new technologies and
convince me to invest time and money creating an application based on
that techology, just to let me down in a couple of year because you just
has invented a new and better technology?

I've been a VFP programmer for years, even before MS buyed out Fox
Company... and I STILL can access data created in 1990!!

If at some time M$ sell us out that you can create and use MDB files in
PDA devices (with eVB for example) they should give us a way to continue
accesing those files with their new technologies.

IMHO

Victor Espina


Paul G. Tobey [eMVP] wrote:
Yep, that's true. The last version of the software that they had was a
while back. They *did* make a significant effort to let everyone know
that support for ADOCE was going away long before it was dropped.
This, of course, favors their own newer database products, which you
might find ominous, but, if it's really valuable to have that
capability, it seems to me that the cost of a commercial wrapper should
be worth it to have support.

Paul T.

Exactly... amazing, uh?

I'm having the exact same problem than you have, and as far I had read
in Internet, MS doesn't offer ANY way to access a MDB in a PDA device.

The only way I have found to access an MDB file in a PDA device is
buying some commercial ADOCE wrapper.

I hope you have more luck than me... if you find any free solution,
please let me know.

Regards,

Victor Espina


Chris wrote:
Ginny,
I'm just installed VS.Net 2005, so I need to find and install the SQL
Server Everywhere ?
And import Access MDB to SQL SE and export to PDA use (what extension
name that I don't know) ?
And therefor I can use your method to access my database file ?

Thanks,

Chris


"Ginny Caughey [MVP]" <[email protected]>
¼¶¼g©ó¶l¥ó·s»D:[email protected]...
Chris,

You might want to try the Access Database Synchronizer for SQL
Everywhere: http://blogs.msdn.com/sqlservereverywhere/

--
Ginny Caughey
Device Application Development MVP


Hello all,

I know we can convert mdb to cdb, but how can I access the .cdb
files in
vs.net 2005 CF ?

someone can provide sample code or else ?

by the way, The files ADOCE.Net in InTheHand Software
(www.inthehand.com)
is removed. (That in the following link)
http://msdn2.microsoft.com/en-US/library/ms837914.aspx


thanks all !


Chris
Click to expand...
Click to expand...
Click to expand...
 
Chris,

For the desktop I think it's called Microsoft SQL Mobile when you're ready
to add references, but the version you get with VS 2005 will only work on
the desktop if you have a development enivornment installed.. This is all
changing, but until SQL Server Compact Edition is released, all I can
recommend at the present is the current CTP.
 
Back
Top