Re: Unreplicate A97 using Graham Seach utility

Tech-Archive recommends: Fix windows errors by optimizing your registry

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



"jacksonmacd" <jacksonmacd@xxxxxxxxxxx> wrote in message
news:1130521384.111744.39310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 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.
>


.

Relevant Pages

  • Re: Unreplicate A97 using Graham Seach utility
    ... Send me your database, because I can't ... >> A2002 version and downgraded it to A97. ... >> If I single-step after the .Append command, ... >> no Unique Index on the primary table. ...
    (microsoft.public.access.replication)
  • Re: Contemplating A97 to A2003
    ... "Leslie Isaacs" wrote in message ... A2003 is more stable than A97 to develop in. ... technology such as PHP to read/write the Access database. ... > 3) a developer whose services I would like to use for some small projects ...
    (microsoft.public.access.conversion)
  • Re: Using Access 97 with Project
    ... "Earl Lewis" wrote in message ... Can the MSP2002 then read the A97 database after its converted? ... Is it possible to keep the Db created with MSP in A2k format and link ...
    (microsoft.public.access.externaldata)
  • Re: Using Access 97 with Project
    ... Can the MSP2002 then read the A97 database after its converted? ... from my A97 app and have them read by MSP. ... I think these are at the heart of my challenge Earl, ...
    (microsoft.public.access.externaldata)
  • Re: Access 2000 - Realtime Development - Should i stick with Access97
    ... Consider keeping your A97 as well as A2000. ... If a database will not convert, use A97 to decompile it first. ... By default, A2000 and 2002 do not include a reference the DAO library, so ... The "Name AutoCorrect" has myriads of bugs and performance problems. ...
    (microsoft.public.access.modulesdaovba)