Split/Merge

[Data Wrangler]

Has anyone used this successfully?

We have a project we want to add some drawings to via exchange, but its being worked on by multiple users. In the past we found that it was best to have everyone out of the project when doing exchanges (Access database).

The idea would be to create a child project, exchange the drawings in and then sync to the parent. I'm assuming that the child project has a separate database, thus avoiding potential problems.

Derek

[HybridAWD]

I've never used Split/Merge and would like to get better with it myself. However, I have exchanged a lot of drawings since I have been in P&ID all which have been very successful. At first I was very lost with the whole exchange setup, but now knowing it, it's a life saver. Same goes for Assembly Manager.

I'll be checking back to this thread to see other peoples input on split merge, im very interested in this as well!

[Data Wrangler]

We exchange drawings all the time, but like I've said above, we have had problems in the past that we could only attribute to having others working in the database when we do so. So our standard procedure is to have exclusive access when we bring stuff in.

I'm hoping to avoid the downtime involved.

Derek

[HybridAWD]

Yeah I can understand why you would want to try and avoid having everyone get out of the project to do this. Especially if you are doing a bunch of the drawings. I'll see what I can dig up about Split/Merge in my training books.

[bioPiper]

Good Morning. I'm reviving this issue because I need a "how to" question answered. Here's my long winded explanation:

Background:
AutoPlant P&ID v8.06
AutoCAD 2006


Project A is running a SQL Server database. User1 wants to take work remotely, both home and project site. I would like to use Split/Merge, but I'm not exactly sure the proper way. Here's what we've done so far.

When using Split/Merge on a SQL Server project, it seems the Child Project must also be a SQL Project under the same Project Root. I say this because I wasn't prompted to use any other database format.

I packaged the project, and unpackaged it onto User1's laptop, using a MSAccess database format.. Everything worked fine, except the APCUSTDIR was not copied into the package zip, and the drawings are referencing the path on the network. (I have given UpdateCustomDir85.exe to User1 to fix the paths embedded in the dwg files, although this should be a function of unpackaging projects.)

How do I get this remote child to replace the existing child on the network. I must be missing something simple in my old age.

The workflow I would like to have seen:

Open Split/Merge.
Create a Child Project ... anywhere I want.
Tell the system which database type I prefer for the child.
Work.
Synchronize.
Rinse and Repeat.

If anyone can help, I'd appreciate it. I've been reading some brilliant answers here forever.

[bioPiper]

Sorry, I wasn't clear above about the project I packaged, and unpackaged to the User1 laptop.

I packaged the Child Project, and unpackaged the Child Project to the laptop.

Thanks.

[bioPiper]

Update:

It turns out that the XM version of Split/Merge has the ability to overwrite existing projects (in this case the child would be overwritten when re-introducing/unpacking the remote data back into the project).

The 8.9 version of Split/Merge cannot be used with an 8.6 project.

Since I can't upgrade the project yet, my solution (Bentley agreed) is to remove the attached child project, delete the modified P&ID's from the Parent project, and exchange them out of the remote child project, and importing them into the original Parent project.

In actuallity, not too onerous. I have to check out the XM version, though.

[dave]

thanks for the follow-up on this bioPiper! It really help when people post questions that don't get resolved to post the resolution when it comes.

GOLD STAR! :D