Trying to use Graham's utility from
http://www.pacificdb.com.au/MVP/Code/UnReplicate.htm
Had problems getting the A97 form to import correctly, so I used the
A2002 version and downgraded it to A97. I removed references to
CurrentProject properly on lines like:
If (Me.chkDeleteExistingObject = True) Or
Len(CurrentProject.AllForms(rsX!Name).Name) = 0 Then
Starting from a fresh database, I can unreplicate the tables and
queries of a typical backend database, but the Relationships are not
being copied. I've single-stepped thru the code, focussing on the
section with the Get All Relations comment:
dbC.Relations.Append relC
dbC.Relations.Refresh
Me.ActionProgress.Value = Me.ActionProgress.Value + 1
If bStop Then GoTo Proc_Exit
Next relX
For the first time thru the code, the Immediate window reports the
Currentdb.Relations.Count = 0 before the .Append line is executed, and
Err.Num is 0. The properties of the relC object appear to be correct.
If I single-step after the .Append command, the count of relations is
still 0, but Err.Num is now 3284 "Index Already Exists"
It appears that attempting to append the relationship also creates an
index, which has already been created earlier.
Next, I commented-out the section that creates the Indexes and ran the
process again on a fresh database. This time, there is an error #3609,
no Unique Index on the primary table.
I am stumped... Is it possible to use this utility on an A97 database,
and copy the Relationships?
BTW - this line:
Me.lblCurrentActivity.Caption = fldX!Name
generates an error message when Error Trapping is turned off. I think
the correct syntax should be fldX.Name.
Graham R Seach - 30 Oct 2005 06:57 GMT
Someone else is having problems too. Send me your database, because I can't
duplicate the problem.
Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
> Trying to use Graham's utility from
> http://www.pacificdb.com.au/MVP/Code/UnReplicate.htm
[quoted text clipped - 39 lines]
> generates an error message when Error Trapping is turned off. I think
> the correct syntax should be fldX.Name.
Jack MacDonald - 30 Oct 2005 15:21 GMT
OK - I can do that from the office tomorrow. It's about 16 MB, don't
know how big it will be when zipped. Is that size OK in an email
attachment?
>Someone else is having problems too. Send me your database, because I can't
>duplicate the problem.
[quoted text clipped - 47 lines]
>> generates an error message when Error Trapping is turned off. I think
>> the correct syntax should be fldX.Name.
**********************
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
Graham R Seach - 31 Oct 2005 10:37 GMT
Jack,
It should be OK. But of course, the smaller the better. :-)
Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------
> OK - I can do that from the office tomorrow. It's about 16 MB, don't
> know how big it will be when zipped. Is that size OK in an email
[quoted text clipped - 57 lines]
> remove uppercase letters for true email
> http://www.geocities.com/jacksonmacd/ for info on MS Access security
Graham R Seach - 31 Oct 2005 10:38 GMT
Jack,
I don't need your data, and you probably don't want that either, so you
might want to just send the schema.
Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------
> OK - I can do that from the office tomorrow. It's about 16 MB, don't
> know how big it will be when zipped. Is that size OK in an email
[quoted text clipped - 57 lines]
> remove uppercase letters for true email
> http://www.geocities.com/jacksonmacd/ for info on MS Access security
Graham R Seach - 03 Nov 2005 08:21 GMT
An updated file has been posted to the website.
Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------
> Trying to use Graham's utility from
> http://www.pacificdb.com.au/MVP/Code/UnReplicate.htm
[quoted text clipped - 39 lines]
> generates an error message when Error Trapping is turned off. I think
> the correct syntax should be fldX.Name.