[AccessD] Convert Replcia to Design Master

[Gustav Brock]

Hi Rocky

That could be anything between a few corrections and a lot of rewriting.

My idea, as a first step to regain control over the database, was to convert to SQL Server, then convert back to the accdb format.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces+gustav=cactus.dk at databaseadvisors.com> På vegne af Rocky Smolin
Sendt: 20. maj 2025 20:47
Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Emne: Re: [AccessD] Convert Replcia to Design Master

Hi Gustav:

How much reprogramming of the front end would a shift to SQL require?

Tia

R

On Tue, May 20, 2025 at 10:29 AM Gustav Brock via AccessD < accessd at databaseadvisors.com> wrote:

> Hi Rocky
>
> Couldn't you use the tool found in the old versions of Access that 
> will upgrade all tables to SQL Server?
> After all, that will not change the current backend in any way, and 
> SQL Server knows about GUIDs (Replica ID).
>
> /gustav
>
> ________________________________
> Fra: AccessD <accessd-bounces+gustav=cactus.dk at databaseadvisors.com> 
> på vegne af Rocky Smolin <rockysmolin2 at gmail.com>
> Sendt: Tirsdag 20 Maj 2025 18:13
> Til: Access Developers discussion and problem solving < 
> accessd at databaseadvisors.com>
> Emne: [AccessD] Convert Replcia to Design Master
>
> Dear List:
>
> I was contacted by a former client who is using Access 97 FE & BE. 
> That solution is no longer effective. They want to switch to a more 
> updated version of office - the target is Office 365.
>
> To go to anything past about 2010 they will need to have the format of 
> the be first updated to 2002-2003 format. Doing this required making 
> changes to the back end.
>
> However the production BE they're using is a Replica and they cannot 
> find the Design Master and all instructions I can find on converting a 
> Replica to a Design Master require the Design Master to be present.
>
> A further complication is that a few of the tables in the BE are 
> corrupted, but they are only using functions which hit the uncorrupted 
> tables, AFAICT.  However, that a side issue.
>
> Doing a direct import of the (uncorrupted) tables does not work. I can 
> copy and paste the records but then the PK gets lost, so the child 
> tables would not have the correct FK. I can do this if I can take off 
> the PK but no design changes are allowed in the Replica.
>
> There is a Relationships diagram so I can see where the FKs might be 
> and I suppose I could read the records from the Replica and, having 
> retrieved the Replica record, save the Replica PK, insert the record 
> into the new back end, the retrieve each of the records in the other 
> tables, and replace the FK there with the new record's PK. But that's 
> a bunch of programming I'm hoping will not be necessary.
>
> So, if there's a way to get this Replica into Design Master format, 
> that would certainly be a shorter distance between the two points.
>
> ANY ideas would be welcome
>
> MTIA,
>
> Rocky