POST
|
I ultimately deleted the domain and recreated it from scratch. No clue what happened or why. I have not had the problem since but we have also upgraded the databases in the meantime.
... View more
02-03-2022
07:15 AM
|
0
|
1
|
623
|
POST
|
This is an outlier database so it's been a while. I'll give it a try and see what happens.
... View more
10-13-2020
03:35 PM
|
0
|
0
|
830
|
POST
|
Yes 100%... I am logged into the server, using the account that has sysadmin, and I can change the domains in the other databases, on the same server, with the same permissions and set-up. (Good question though, I went and double checked to make sure) I also tried doing this via python, which usually works, and it also failed. Even though the code reported success.
... View more
10-13-2020
01:33 PM
|
1
|
2
|
830
|
POST
|
I manage several multi-user geodatabases (SQL, Versioned, 10.5.1) and have never had a problem with adding a new coded domain value to an existing domain set in any of the databases. Currently I am having an issue with one of the databases not retaining the new coded domain. Workflow*: Add a new coded value, it is there and everything appears fine. Apply and refresh the database, value is still present. Close and reopen ArcCatalog, open the database and the value is gone. I found a similar post at How to add a new code value to existing domain? but the solution did not fit with the issues I am having. There are no Subtypes, the domain is correctly connected to the field and all the existing codes work correctly. I am owner and DBA for the database and this same layer happens to be in one of the other databases I manage. The domain applied correctly and with no problems in that database.
... View more
10-13-2020
10:16 AM
|
0
|
8
|
871
|
IDEA
|
Great idea! We recently had our VM go down and portal authenticated users, on that VM, were given only 1 hour. Fortunately we got the VM back up but what if it had taken a few hours?
... View more
01-28-2020
09:14 AM
|
0
|
1
|
969
|
IDEA
|
In addition you can no longer import dBase files into Access (2013 or newer) so the only way I can easily talk between my GIS tables and Access, without a ton of reformatting, is to store it as an pGDB (.mdb) and then import into Access or save it to an older version. There is so much communication I do between tabular data (coming and going from access/excel users) and my GIS files. That will be lost if they cut pGDB. FYI excel and txt does not cut it.
... View more
05-26-2017
02:01 PM
|
4
|
1
|
7037
|
Title | Kudos | Posted |
---|---|---|
1 | 10-13-2020 01:33 PM | |
4 | 05-26-2017 02:01 PM |
Online Status |
Offline
|
Date Last Visited |
02-28-2024
03:42 PM
|