Hi Gang,
Thank you for the replies and advice. Taking this all into consideration here is the latest on this perplexing issue...
LATEST ANALYSES:
1) I noticed that no matter what log I put in (I have a number of queries) it does the same thing.
2) Did a full defrag-repair and tried again. Still no joy.
3) Carved the database down to ten records and tried it (an aggressive "binary search" approach![wink.gif]()
). SURPRISE - that worked. So I am inclined to believe there is something goofy in the GPX file in my Pocket Query as well. That file is here if anyone is interested: http://www.yjprod.com/image/MISC/TG10.zip
4) Took the original Pocket Query GPX files (main and waypoint file) into Notepad++ and replaced all NULLs with "nothing". Re-imported. No joy.
5) Started with a new file (after messing with the nulls in the one above). Removed the waypoint file from the downloaded Pocket Query archive entirely. Re-imported. Threw the error again, but *acted* like it imported (very brief progress bar)...but didn't.
6) Went through the remaining Pocket Query archive's file (sans waypoint file) and replaced NULL characters (zero occurrences). No joy.
7) Did a Defrag-Repair on the above. Still no joy.
8) Went into the "Geocache TourGuide.gpx" with Notepad++ and replaced NULL characters (it found one). Did an export...acted like it worked (no error). Checked on GPS. Looked like it worked (a very brief progress bar again) except it only looks like 30 of the 1000-or-so caches actually loaded. YAARGH!![mad.gif]()
9) Tested a query in three *entirely different* geographic regions of the country to see if it's a single cache in the local area that is the issue. No joy.
RESULTS:
1) Based on the results above, I think it's fairly safe to conclude that *something* in the Pocket Query data is causing the problem.
2) The problem exists on *every* single query I have no matter the geographic locale.
3) The null character cut on the "Geocache TourGuide.gpx" file only removed one (1) NULL character, but allowed about 30ish records to import.
SOME FOLLOW-ON QUESTIONS:
1) Just to qualify, is it the "Geocache TourGuide.gpx" file I should be killing NULL characters in, or the original file from the query? I have tried both.
2) Here is an example of one of the original Pocket Queries: http://www.yjprod.com/image/MISC/HR.zip
It would be interesting to see if anyone can load it up without getting this error.
3) I am using GSAK's latest (v8.3.0.1) and whenever I run the query, it has a large, whiny box that indicates "Macro is using the following deprecated commands and/or functions: SET..." (see image below). Not sure if this is a problem, but noting it anyway.
![user posted image]()
This is certainly a nutty one.![wacko.gif]()
Thank you for the replies and advice. Taking this all into consideration here is the latest on this perplexing issue...
LATEST ANALYSES:
1) I noticed that no matter what log I put in (I have a number of queries) it does the same thing.
2) Did a full defrag-repair and tried again. Still no joy.
3) Carved the database down to ten records and tried it (an aggressive "binary search" approach
). SURPRISE - that worked. So I am inclined to believe there is something goofy in the GPX file in my Pocket Query as well. That file is here if anyone is interested: http://www.yjprod.com/image/MISC/TG10.zip4) Took the original Pocket Query GPX files (main and waypoint file) into Notepad++ and replaced all NULLs with "nothing". Re-imported. No joy.
5) Started with a new file (after messing with the nulls in the one above). Removed the waypoint file from the downloaded Pocket Query archive entirely. Re-imported. Threw the error again, but *acted* like it imported (very brief progress bar)...but didn't.
6) Went through the remaining Pocket Query archive's file (sans waypoint file) and replaced NULL characters (zero occurrences). No joy.
7) Did a Defrag-Repair on the above. Still no joy.
8) Went into the "Geocache TourGuide.gpx" with Notepad++ and replaced NULL characters (it found one). Did an export...acted like it worked (no error). Checked on GPS. Looked like it worked (a very brief progress bar again) except it only looks like 30 of the 1000-or-so caches actually loaded. YAARGH!
9) Tested a query in three *entirely different* geographic regions of the country to see if it's a single cache in the local area that is the issue. No joy.
RESULTS:
1) Based on the results above, I think it's fairly safe to conclude that *something* in the Pocket Query data is causing the problem.
2) The problem exists on *every* single query I have no matter the geographic locale.
3) The null character cut on the "Geocache TourGuide.gpx" file only removed one (1) NULL character, but allowed about 30ish records to import.
SOME FOLLOW-ON QUESTIONS:
1) Just to qualify, is it the "Geocache TourGuide.gpx" file I should be killing NULL characters in, or the original file from the query? I have tried both.
2) Here is an example of one of the original Pocket Queries: http://www.yjprod.com/image/MISC/HR.zip
It would be interesting to see if anyone can load it up without getting this error.
3) I am using GSAK's latest (v8.3.0.1) and whenever I run the query, it has a large, whiny box that indicates "Macro is using the following deprecated commands and/or functions: SET..." (see image below). Not sure if this is a problem, but noting it anyway.
This is certainly a nutty one.
