iAssemblies Needing Regenerated

[meck]

I have iLogic code that will insert an iassembly into a main assembly and then changes the iassembly to the correct member for the that job. All of the model files are located in the same directory. It works perfectly as long as the user is using the folder where they are initially stored. We'd like to give the models to other groups in our company to use. We have a PRM system, not Vault, where we store the files. If the user gets the files from the PRM and runs the program, the iassemblies are installed in the main assembly, but an error occurs when trying to set the member saying it cannot find the file. The iassembly member folders are all there as are the files inside the folder. We make sure the user is using the Inventor project inside the main assembly's folder.

I first thought it was something to do we our PRM, so I uploaded all the model files to a share point site and went through all the iassemblies and made sure they were all regenerated. My sync'd files work fine, but when someone else downloads the files from share point, the code errors again saying it cannot find the file.

I do not think it is my code, but I am using iPart.ChangeRow(OccurNo, PartNumber). I believe is it something to do with the iassemblies not "seeing" the member files, because the user can regenerate the members and the code will work. There are hundreds of iassemblies so making the user manually regenerate the files is not possible. I even created code to regenerate the files after downloading, but it still doesn't help. There is something missing that manually regenerating the files fixes.

Can someone please explain what is going on that is causing this problem?

Thanks!

[A.Acheson]

One thing to know is when iparts /iAssembly files are generated they need a folder named as the occurrence name of the factory they are generated from. I wonder if this folder missing is the issue with file referenced missing? I would think that you also need to do a pack and go from the original source to preserve the links. 

Any chance of some error messages and the workflow that let to them? Can you carry out a pack and go of the assembly isolated from PRM. This way you can isolate the PRM interactions. Then it will be down to file referencing or ilogic interaction. 

Can you suppress the ilogic rules and carry out only manual member changes of the ipart/iassembly  and keep a look out  on the member folders for changes? This hopefully will isolate ilogic interactions and get a picture of how the files are connecting  

This would also be a good question for the inventor forum as it may not be totally an ilogic interaction causing this. 

[WCrihfield]

You originally said the others within the company were attempting to use the files from the same shared file location originally, right?  I'm not sure what PRM may stand for in your case, but something comes to mind that you could check out.  At one point our team was having problems because, even though we were all sourcing our files and settings from the same place on the network, some had a different 'mapped network drive' letter than others for one of the main locations.  To eliminate the problems that was causing we eliminated the use of that drive letter, and included the full network path to the resources in all our settings for each user in our team.

[meck]

Thank you for the reply. As I said all the folders containing all of the iassembly members are there in the same folder as the rest of the files. I am not sure pack-n-go is feasible. From what I know about pack-n-go you right click on an assembly and that assembly and its files are copied to the new location. I have hundreds of assemblies that need to be copied. 

You may be correct. It may not be a iLogic issue but a linking issue with the iassembly factory and its members. I will place this question to the general forum also.

[meck]

Thanks for replying.

If any of the users use the files in their original location everything works. We would rather not allow user in the satellite office to make changes to our files so we only want to give them copies. There really is no mapping issue that I can see.

Regards