Basecamp changing many address on it's own.

Former Member over 5 years ago

Here is a summery of my problem. This has happened three times now. In order to fix it you have to delete all the waypoints and re-enter them. I went to a known good backup (I have many) and it would not properly load the file without the same kinds of errors. I primarily use a Mac, but I have the exact results on a PC.

It is strictly a Basecamp issue. No device is connected.

Basecamp version: 4.7.0

Mac operating system version: 10.12.6

Here is what happens: After making some minor waypoint changes to my collection, MANY of the way-point's already in the collection address change. This is the address that displays on my 665 (I have 3 of them) when you look at a waypoint.

I'M TOTALLY FRUSTRATED after 3 times

0 SUSSAMB over 5 years ago

Are these different waypoints or the same waypoint in different folders/files? BaseCamp is a database so if you have multiple entries of the same waypoint then changing one will change the others

0 Former Member over 5 years ago

These are all different waypoints, on different lists and some even in different folders. I worked in database management for a while so I'm failure with how they work. Also, I've used Basecamp since day one and consider myself pretty good at it.

Two exports to a .csv and the differences are numerous.

0 SUSSAMB over 5 years ago in reply to Former Member

Have you recently updated BaseCamp? Can't think of any other reason why its behaviour should suddenly change.

0 Former Member over 5 years ago in reply to SUSSAMB

Nope. Like I said, this isn't the first time Basecamp did this to me. It seems that every time I update maps I have this problem. The biggest thing I can't understand is I can do a backup of a perfectly working collection. Then when I do a restore it's messed up. I wish I could attach the files.

I'm not the most current version because I won't update my Mac OS. They went to 64bit only programs. I have a lot of 32bit programs I paid a lot of money for that I'd have to re-buy. That isn't happening.

I've send the files to Garmin, we'll see what they have to say.

0 TekRider over 5 years ago

Since your on macOS 10.12.6 I'd recommend downgrading BC to 4.6.3 and resist the urge to update. Before downgrading export your collection out for re-import after installing 4.6.3. I can tell you there's other issues with 4.7.0 you probably just haven't run into yet.

0 Former Member over 5 years ago in reply to TekRider

OK, I'm wiling to try that. Where can I download 4.6.3? I can only 4.8.8 on Garmin's site.

0 SUSSAMB over 5 years ago in reply to Former Member

http://www.gawisp.com/perry/macintosh/ have them all

0 Former Member over 5 years ago in reply to SUSSAMB

I've DL 4.6.3 and installed it. I still get the same results. If I try to batch edit, the data gets corrupted. If I edit one at a time it does not.

I've tried working with smaller numbers (30) waypoints to save time.

0 danham_ over 5 years ago

Does the address change in BC, or just on the 665? The reason I ask is because I'm wondering if different map versions on the device versus Mac could be at the root of this. Does the address change to a very different location, or does it "creep" down the street a little bit? The latter might point to the version problem. I have definitely noticed waypoints moving (though I didn't check street addresses) when comparing their position on an older map version to a new one while pre-flight testing a route I have created under the old version.

0 Former Member over 5 years ago in reply to danham_

I'm only working in Basecamp. No GPS attached.

It seems to pick a random address from one of my waypoints and use that. The ones it changes also varies.

The location always seems correct, just the address that displays when you look at a waypoint on the gps. The address in the information box is always correct.

Have you ever exported to a csv file ald looked at it in excel?

I'll tell you what, here is my e-mail [email protected] e-mail me and I'll send you the files to look at. Easier than going back and forth here.

BTW, THANK YOU very much for your time.