Re: Replacement for Jet provider in application for XP Embedded

"Corey" <Corey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:864B022B-B05D-4BC7-A1B3-BB84A41A04FD@xxxxxxxxxxxxxxxx


"Bogus" wrote:

=?Utf-8?B?Q29yZXk=?= <Corey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"BogusID" wrote:

"Corey" <Corey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4D02E55A-D6E9-4F27-A6FE-3176D079EE36@xxxxxxxxxxxxxxxx
I'm trying to get a POS app I wrote in VB 6 to work on a thin client
using
XP
Embedded. My connection string utilizes the
"Microsoft.Jet.OLEDB.4.0"
provider and I've read that XP Embedded does not use the Jet engine.

What should I use as my new provider and if using a different
provider
is
the key, does that mean I'm going to have to change all my code
related
to
how I access and deal with my recordsets? (All data access and
modification
is occuring manually via code and NOT via Active X Controls)

Help and thanks,

Hello Corey,

Can you download and install the Microsoft Data Access Components onto
the
embedded system?
Does it have a hard drive, or flash with application space available
for
the
Program Files\Common folder?

Usually embedded devices have a subset of the OS, so data access may
be
'optional'...


<http://www.microsoft.com/downloads/details.aspx?DisplayLang=en&FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c>

Regards,
David


David,

No hard drive, just flash space. It's a Neoware Thin Client with plenty
of

space, and the flavor of XP Embedded is supposed to the data access stuf
loaded with the OS, however when I my app starts up and reaches the
point
in
source where I set my connection string, I get a run time 3706 "provider
cannot be found".

Can I just install Jet 4.0 on the thin client to make this work, or just
the
latest version of the MDAC before it was retired?

Thanks,


I would insure having system admin rights, and install MDAC 2.8.

Next i'd review the programs connection string to insure it's using the
correct format.
Provider=Microsoft.Jet.OLEDB.4.0; Data Source=C:\path\filename.mdb; User
ID=admin; Password=;

Let us know if this helps...David



That is exactly how my connection string is setup. My POS app works just
fine on Win2K and WinXP Pro/Home. I'll see about installing MDAC 2.8 and
I'll let you know.

Thanks again,



Fingers crossed, make sure you have proper rights!


.

Relevant Pages

  • Re: Replacement for Jet provider in application for XP Embedded
    ... provider and I've read that XP Embedded does not use the Jet engine. ... What should I use as my new provider and if using a different provider ... I would insure having system admin rights, and install MDAC 2.8. ... Next i'd review the programs connection string to insure it's using the ...
    (microsoft.public.vb.database)
  • Re: Replacement for Jet provider in application for XP Embedded
    ... provider and I've read that XP Embedded does not use the Jet engine. ... What should I use as my new provider and if using a different provider ... Can I just install Jet 4.0 on the thin client to make this work, ... Next i'd review the programs connection string to insure it's using the ...
    (microsoft.public.vb.database)
  • RE: Database Lookup Functoid Connection String
    ... A OLE DB provider is a COM component which implement a number of COM ... And connection string is a way to initialize a OLE DB provider. ... accessed by the BizTalk server account, ...
    (microsoft.public.biztalk.general)
  • Re: Need ODBC driver for DBF files for VISTA
    ... Can you use the FoxPro and Visual FoxPro OLE DB data provider, ... your connection string is incorrect. ... refer to the DBF itself by name and without the DBF extension, ... VS6 and will not be tested or updated to work with Windows Vista. ...
    (microsoft.public.vb.database)
  • Re: SQL Server 2005 Express connection error?
    ... Hard-code the provider and connection string and see if that works. ... //Obtain the database connection string ... //Create a database specific command object ...
    (microsoft.public.dotnet.framework.adonet)