Jet Replication in Access 2007

[Peter]

Hi,

i've got an older Access program, which is written in the version 2000
and i'd like to use it with my new office 2007, so access 2007.

In the program, there is an replication written with the Jet Replica
Library, and i read on a microsoft site, that replications in jet
schould still work in access 2007, if you still use the old
extension .mdb

so i tried it, but there comes the error -2147467259 - "The Microsoft
Office Access - Databasemodul was not initialized."

Here is the connection-string, i use to connect to the replicable
datafile:
"Provider=Microsoft.ACE.OLEDB.12.0;User ID=Entwickler;
Password=qwerASDF12;Data Source=c:\Programme\BAP
\BAP_Prog_V13_FINAL.mdb;Mode=Share Deny None;Extended
Properties="";Jet OLEDB:System database=c:\Programme\BAP\BAP.mdw;Jet
OLEDB:Registry Path=Software\Microsoft\Office\12.0\Access\Access
Connectivity Engine;Jet OLEDB:Database Password="";Jet OLEDB:Engine
Type=5;Jet OLEDB:Database Locking Mode=1;Jet OLEDB:Global Partial Bulk
Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database
Password="";Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt
Database=False;Jet OLEDB:Don't Copy Locale on Compact=False;Jet
OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False;Jet
OLEDB:Support Complex Data=True;"

and here is the code, i use to replicate the data:

Dim repMaster As New JRO.Replica

repMaster.ActiveConnection = GetJetConnection(GetINIData("Pfade",
"Daten"))
repMaster.CreateReplica strPfad, "Repliziert Daten von BAP"

Does anyone has in idea?
The Office 2007 is installed complete. I also tried to change the Jet
OLEDB:Engine Type to version 6, but this also didn't help anything.

Thank you very much.

[David W. Fenton]

Peter <pe*********@gmail.comwrote in
news:c9**********************************@x41g2000 hsb.googlegroups.co
m:

i've got an older Access program, which is written in the version
2000 and i'd like to use it with my new office 2007, so access
2007.

In the program, there is an replication written with the Jet
Replica Library, and i read on a microsoft site, that replications
in jet schould still work in access 2007, if you still use the old
extension .mdb

so i tried it, but there comes the error -2147467259 - "The
Microsoft Office Access - Databasemodul was not initialized."

Here is the connection-string, i use to connect to the replicable
datafile:
"Provider=Microsoft.ACE.OLEDB.12.0;User ID=Entwickler;
Password=qwerASDF12;Data Source=c:\Programme\BAP
\BAP_Prog_V13_FINAL.mdb;Mode=Share Deny None;Extended
Properties="";Jet OLEDB:System
database=c:\Programme\BAP\BAP.mdw;Jet OLEDB:Registry
Path=Software\Microsoft\Office\12.0\Access\Access Connectivity
Engine;Jet OLEDB:Database Password="";Jet OLEDB:Engine Type=5;Jet
OLEDB:Database Locking Mode=1;Jet OLEDB:Global Partial Bulk
Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database
Password="";Jet OLEDB:Create System Database=False;Jet
OLEDB:Encrypt Database=False;Jet OLEDB:Don't Copy Locale on
Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet
OLEDB:SFP=False;Jet OLEDB:Support Complex Data=True;"

This is an OLEDB connect string, and makes no sense, since you can't
have linked tables with ADO.

and here is the code, i use to replicate the data:

Dim repMaster As New JRO.Replica

repMaster.ActiveConnection = GetJetConnection(GetINIData("Pfade",
"Daten"))
repMaster.CreateReplica strPfad, "Repliziert Daten von BAP"

Does anyone has in idea?
The Office 2007 is installed complete. I also tried to change the
Jet OLEDB:Engine Type to version 6, but this also didn't help
anything.

Why are you using OLEDB?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Peter]

Why are you using OLEDB?

I just take the connection string from the currentproject and add a
password and change the Data Source property to connect to the other
database, because i tried to connect to it, as it is shown in the
msdn, but it didn't work, so i tried it this way and with access 2000
and 2003 it worked

so you mean the connection string is wrong, and i have to change it?

[David W. Fenton]

Peter <pe*********@gmail.comwrote in
news:9e**********************************@d1g2000h sg.googlegroups.com
:

>Why are you using OLEDB?

I just take the connection string from the currentproject and add
a password and change the Data Source property to connect to the
other database, because i tried to connect to it, as it is shown
in the msdn, but it didn't work, so i tried it this way and with
access 2000 and 2003 it worked

so you mean the connection string is wrong, and i have to change
it?

I don't know how you manage to get an OLEDB connect string for your
current connection. Then again, I've never used any form of
ADO/OLEDB, so maybe I'm confused. I'd think your front end would
have linked tables (which are, by definition, DAO). Of course,
you're using JRO, which works counterintuitively, because it's one
of the ugly stepchildren of the ADO debacle.

I don't have any advice to offer, except to dump JRO, which never
made the slightest sense to me in the first place.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Peter]

I just take the connection string from the currentproject and add

a password and change the Data Source property to connect to the
other database, because i tried to connect to it, as it is shown
in the msdn, but it didn't work, so i tried it this way and with
access 2000 and 2003 it worked

so you mean the connection string is wrong, and i have to change
it?

I don't know how you manage to get an OLEDB connect string for your
current connection. Then again, I've never used any form of
ADO/OLEDB, so maybe I'm confused. I'd think your front end would
have linked tables (which are, by definition, DAO). Of course,
you're using JRO, which works counterintuitively, because it's one
of the ugly stepchildren of the ADO debacle.

i just take CurrentProject.Connection
and yes there are linked tables in the forntend
and firstly i programmed the synchronization in DAO, but this isn't
supported by Access 2007 anymore, so now i had to recode it using JET
whichs works in the older Access versions as the DAO but doesn't work
in Access 2007

[David W. Fenton]

Peter <pe*********@gmail.comwrote in
news:26**********************************@a1g2000h sb.googlegroups.com
:

I just take the connection string from the currentproject and
add a password and change the Data Source property to connect
to the other database, because i tried to connect to it, as it
is shown in the msdn, but it didn't work, so i tried it this
way and with access 2000 and 2003 it worked

so you mean the connection string is wrong, and i have to
change it?

I don't know how you manage to get an OLEDB connect string for
your current connection. Then again, I've never used any form of
ADO/OLEDB, so maybe I'm confused. I'd think your front end would
have linked tables (which are, by definition, DAO). Of course,
you're using JRO, which works counterintuitively, because it's
one of the ugly stepchildren of the ADO debacle.

i just take CurrentProject.Connection
and yes there are linked tables in the forntend
and firstly i programmed the synchronization in DAO, but this
isn't supported by Access 2007 anymore, so now i had to recode it
using JET whichs works in the older Access versions as the DAO but
doesn't work in Access 2007

Eh? Yes, of course, DAO is still supported in A2K7. However, there
was a bug in the initial shipping release of A2K7 that caused DAO
synchs to fail, but that was fixed (first by a hotfix, and then in
the first service pack).

The idea that JRO would be preferable in A2K7 is ridiculous, as MS
is deprecating ADO (and its ugly stepchildren) for work with Jet
data. DAO is the way to go -- it's the live, in-development data
interface for Jet data. ADO/JRO on the other hand, are completely
dead.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/