Thanks Clyde and Red Roo, but I have abandoned the use of any of the macros calling for the use of POI Loader. It's way too unstable and none of us are even remotely thrilled with fighting with it and the Garmin engineers. I went there with my 60CSx macro and am not interested in returning.
As the GSAK-generated GPX file in the POI_Loader folder was intact and readable by other programs, I'm fairly confident it's a Garmin issue (and not GSAK or GPSBabel). Its randomness and non-nondescript error messages, mixed with a dose of machine configuration peculiarities makes it obviously tough to troubleshoot. Sorry Red Roo, but your macro can't get around that. Please keep in mind I created a completely new database, downloaded the offending cache from gc.com, deleted all the logs, and STILL had the problem. Clyde, is right. There doesn't appear to be anything we can do.
At this point, I'm using and very content with Lignumaqua's NuviExport macro. It's a one-step process and works as expected. Mike, I'm going to send you a private email with why I thought it wasn't working earlier.
Again, thanks everyone ... we tried!
Mike
As the GSAK-generated GPX file in the POI_Loader folder was intact and readable by other programs, I'm fairly confident it's a Garmin issue (and not GSAK or GPSBabel). Its randomness and non-nondescript error messages, mixed with a dose of machine configuration peculiarities makes it obviously tough to troubleshoot. Sorry Red Roo, but your macro can't get around that. Please keep in mind I created a completely new database, downloaded the offending cache from gc.com, deleted all the logs, and STILL had the problem. Clyde, is right. There doesn't appear to be anything we can do.
At this point, I'm using and very content with Lignumaqua's NuviExport macro. It's a one-step process and works as expected. Mike, I'm going to send you a private email with why I thought it wasn't working earlier.
Again, thanks everyone ... we tried!
Mike
