I have a split database running under Access 2003 which uses a programmatic
sync. This database has been running for several years, with sync both ways
working fine.
Now, as the world turns, I'm testing it with the released Vista and Office
2007. Much of the code runs fine - a few problems with focus, and filters -
but the sync just flat out does not work, giving an "ERROR: 3251 Operation
is not supported for this type of object."
The code, extracted from the database and run from a button on a form, was
placed in a clean database, and is listed below. Same error using
dbRepImportChanges.
I've tried to manually sync the two replicas and that works with no
problems.
David Groome
MicroMetric, Inc.
The code
is -----------------------------------------------------------------
'--------------------------------
' Synchronize Data
' This routine updates the Local data with the Server changes
'--------------------------------
Private Sub cmdUpdateLocal_Click()
On Error GoTo Err_Rtn
Dim dbsMICROData As Database
Dim booMasterData As Boolean
Dim booLocalData As Boolean
Dim FSO
'Test first for file present
Set FSO = CreateObject("Scripting.FileSystemObject")
booMasterData =
FSO.FileExists("Z:\data\access\MICRO\Data\MICRODataR.mdb")
booLocalData =
FSO.FileExists("C:\data\access\MICRO\Data\MICRODataR.mdb")
MsgBox "Master Data-" & booMasterData & " Mobile Data-" &
booLocalData
'Perform Sync
DoCmd.Hourglass True
Set dbsMICROData =
OpenDatabase("C:\data\access\MICRO\Data\MICRODataR.mdb")
dbsMICROData.Synchronize "z:\data\access\MICRO\Data\MICRODataR.mdb",
dbRepExportChanges
' (ERROR occurs on the prior statement)
MsgBox "Sync Update Local without error"
dbsMICROData.Close
Exit_Rtn:
DoCmd.Hourglass False
Exit Sub
Err_Rtn:
MsgBox "ERROR:" & Err.Number & " " & Err.Description
Resume Exit_Rtn
End Sub
end code--------------------------------------------------------------------
David W. Fenton - 19 Dec 2006 18:52 GMT
> The code, extracted from the database and run from a button on a
> form, was placed in a clean database, and is listed below. Same
> error using dbRepImportChanges.
Do you have the correct DAO reference? I'd also make sure I qualify
Dim db as DAO.Database (not that this will fix the problem).

Signature
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Kirk Groome - 31 Dec 2006 03:50 GMT
Hello all,
Well after working the problem and not finding a fix I called Microsoft.
After working with them they say there is a bug in access 2007. None of the
VBA reclication calls will work for DAO. They are thinking about a hot fix
for this problem but it is going to be a few months before they have the fix
so as of now you have to use the user interface to sync or recode for
jrsync. If you are having this problem let me know and I will give you the
the lastest info I have. I will also let you knowl how to tell microsoft
that this is a problem for more then just me.
I will also post when the hot fix is released.
>I have a split database running under Access 2003 which uses a programmatic
>sync. This database has been running for several years, with sync both ways
[quoted text clipped - 59 lines]
> end
> code--------------------------------------------------------------------
David W. Fenton - 31 Dec 2006 19:56 GMT
> Well after working the problem and not finding a fix I called
> Microsoft. After working with them they say there is a bug in
[quoted text clipped - 7 lines]
>
> I will also post when the hot fix is released.
Could you please go to my Jet Replication Wiki:
http://www.dfenton.com/DFA/Replication/
create an account for yourself, and post something in the "Resources
for learning about Jet Replication"? I'd put it as an additional
paragraph under the heading there "Things not to believe in the MS
documentation" (or in the article for that topic).
Also, can you post this to comp.databases.ms-access and
microsoft.public.access? This needs to be more widely known.

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