Thanks guys, I posted this and then saw another thread on the topic. The problem has been solved by locating everything on the local machine (we had been running on a network) Eric
I have had the same problem and took me a few days to figure out. Here are a few things to consider...1) I use relative paths in all of my ArcGIS projects. Trimble positions seems remembers the absolute path so to speak. I had issues because I mapped a drive on the server directly to the project I was working on. When I created the original project I went to the server and then to my project. I now know that this is one way to create a similar error you are talking about. In summary the Trimble Positions database that is created in the background stores the absolute path to your data, at least that's what I have found. It actually makes sense when you think about it.2) If you are working from a server, try and copy the check in project onto your local machine and check it in. I know this is contrary to what is said above but this also worked for me. 3) A am still having problems checking in data from the server environment but use #2 as a work around.4) I looked into the JIT stuff and don't think that's the answer5) Good Luck.! Keep on trying, you will get it working. We are both ahead of the game.Another thought... Are you checking out shapefiles? If you are I could not get this to work at all! In my workflow I create quick projects using geodatabases. I only check out the Schema for my editing files and use background data axf files for my base (counties, etc)
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか?無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.