POST
|
I built a customized .mxd that uses VBA code (in ArcMap 8x). During the MxDocument OpenDocument event, I get a reference to the application and implement LockCustomization. This worked in ArcMap 9x also. But in 10.0 it's causing an error because 10.0 apparently references MS Access during start-up. So I can't use my customization filter because there's already an active lock created by MS Access. I know the error is caused by MSAccess because if I open the .mxd on a computer I've never been on before, the MS Access screen opens DURING THE ARCMAP START-UP and asks me to enter my name and initials (just like it would if I was opening MS Access for the first-time use). Why is ArcMap 10.0 calling MSAccess during start-up, and how do I prevent MSAccess from causing a lock? (Yes, I know VBA won't work in 10.2, but I'm in 10.0 .)
... View more
04-02-2013
09:55 PM
|
0
|
0
|
468
|
POST
|
I just tested the autoload method of an Add-In ArcMap Application Extension. That mode causes the extension to automatically fires up at ArcMap start. ... Admittedly, this is not as easily done as creating and storing a template map, but it does provide at least one method for acheiving the same end result that is not document based. I am struggling to keep the UI custom tools I built in my 9.3 mxds into my 10.0 mxds. First problem is that I had to get an ESRI auth# for the VBA extension for 10. Then, I notice "Application.Document" no longer gets the document, so I changed all those to ThisDocument, which allowed the .mxd to open the OpenDocument function correctly. Some of my tools are still working. Some do not, because other ArcObjects have changed their methods or properties. Where can I go for help? I know nothing about Add-In appl extensions. Where can I find a programmer for hire that can convert my code from 9.3 to 10?
... View more
10-23-2012
10:44 PM
|
0
|
0
|
674
|
POST
|
I am experiencing the same problem. I think it began when we switched to the Microsoft Office suite that creates .docx instead of .doc, etc. Prior to that switch, my maps printed from .pdf were the same color as the maps printed from an open .mxd. Now during the export, the colors are altered. The .pdfs themselves have different colors. I've been unable to correct the problem. (It is possible there was some kind of Adobe Reader upgrade at the same time as the Microsoft Upgrade. Perhaps a different color library was installed?) It is disappointing. If anyone can offer any guidance, I'd love to hear it!
... View more
01-17-2012
11:57 AM
|
0
|
0
|
395
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|