Running POWERGEOPAK v8i- (ss4) version = .845
Alert message, states "GEOPAK has detected an older version of this gpk file. Do you wish to create a backup of this file as j97X:\.gpk, then create an updated version?" .
There is not even a j97X:\.gpk. The one post, states the fix is to have a Letter Directory, not // type path. that is not my issue. My directory path is " X:\projects.....".
I am able to hit NO, and exit. and restart geopak-project manager, and then i do not get the Alert message. Seems very random, too. And this is happening on multiple users computers.
I am working on a project that was created in Geopak SS2, now want to make changes using PowerGeopak SS10 and getting the message that I need to open Coordinate Geometry to "convert" the .gpk to the new version. The conversion does not seem to happen by just opening COGO. How do I convert the .gpk to be compatible?
it really seemed like i do not want to convert the gpk. after some testing, and not converting the gpk, my workaround is simply to cancel the prompt, close my geopak session, and exit my drawing. When i re opened, the message does not appear, and i can access my gpk, as usual. Its like the convert message only occurs, when our shared network ( we went to Panzura) does a backup, in its system. Not the exact fix, but a simple step, that has allowed us to maintain the gpk, without trying to convert it.
labeler still works along with draw existing cross sections; it was only when i went to process proposed cross sections that i got the message that the xxxjob.gpk was not compatible and needed to be converted. Will have to find a workaroud also.
This is something I'm running into just now. To add more from my experience:
I wasn't sure what "cancel the prompt" means. Intuition told me you meant no, so I took that option. I was warned that the file couldn't load. Inquisitive as I am, I went into cogo, entered "list cha *" and found that none were in the file.
After this, I closed my session as Cory did, reopened, then did the same steps except this caution didn't come up at all. When I went into cogo and entered the same command, I saw that everything was listed.
I wish I knew why this comes up at all, but knowing what you can expect goes a long way, so there it is.