Latest Contributions by JoshuaBixby

Ah Luke, don't fall for the Esri excuses!  ArcGIS Pro doesn't support personal geodatabases because Esri doesn't want it to, that is it.  The references to Microsoft retiring the Jet Database Engine and that the Jet Database Engine never had a 64-bit library are true, but that is only half the story, the half where Esri can blame another organization for their business decision to not support personal geodatabases in ArcGIS Pro. Shortly after the Microsoft SQL Server team announced retirement of the Jet Database Engine, the Microsoft Office team announced they would continue to support MS Access through a new Access Connectivity Engine (ACE).  All signs point to ACE being a forked version of Jet that the MS Office team continued development on themselves.  Additionally, and most importantly, the MS Office team already stated in 2005: From A discussion of what's new in Access 12 : Access 12's new data engine: This means Access 12 no longer uses the system Jet engine, but is tightly bound to its own version.  The new version is fully backwards compatible with the old, so it will read & write files from earlier versions without any problems.  So in 2005, ten years before ArcGIS Pro 1.0 was released, Microsoft had already stated they would have a 64-bit, backward compatible database engine that would work with Jet-based MDB files. The real kicker is that ArcGIS Pro accesses Excel files using the Microsoft Access Database Engine drivers. From Install the drivers to work with Microsoft Excel files—ArcGIS Pro | Documentation Microsoft Access Database Engine technology helps bridge communication and external data transfers between files that are proprietary to the Microsoft Office system and other non-Microsoft Office applications such as ArcGIS Pro. So the MS Access Database Engine drivers are necessary for ArcGIS Pro to open Excel files, the same drivers natively open old (*.mdb) and new (*.accdb) Access files, and yet somehow opening personal geodatabases in ArcGIS Pro is a bridge too far for Esri to cross.  <insert head shake> ... View more

What you are experiencing is expected behavior, not just for ArcGIS Pro but for SQL in general.  NULL is neither TRUE or FALSE, it is UNKNOWN.  In your case, the results do not return NULL records because the database engine evaluating the query has no idea whether the NULL record is one of the values you want to exclude.  Only results that are guaranteed to be TRUE are returned by the query. It is always best to handle NULL records explicitly, like you are already doing with the "IS NULL" logic. ... View more

The answer is yes, but it isn't out-of-the-box functionality.  What is an SOI | ArcGIS Enterprise SDK ... View more

@DrewFlater, I don't know if what Bud and I have in mind are exactly the same, but they are similar enough to merge for discussion on the requests. Looking at the original example, it appears the OP is asking for a pairwise combination, one might call it "zipping".  I am more interested in a cross product that results in a straight combination if multiple fields are selected.  For example, OBJECTID PRJTID MUNICIPALI ZIPCODE 2 2 A 1 3 2 A 2 4 2 B 1 5 2 B 2   The main use case I have run across is a form of re-normalizing tables from data warehouses.  Re-normalizing redundant attribution can be as straightforward as removing columns, but when information has been concatenated for reporting purposes the attribution needs to be exploded. I realize there is readily available code for doing this task, and I am a big advocate for scripting over GUI-driven clickops, but I also work in and support an organization with tens of thousands of GIS users and a vast majority of those users solely rely on the GUI and geoprocessing tools. ... View more

Bud, I thought I saw a similar idea in the past but couldn't find it while searching, hence me posting it.  For now, I will leave my idea up too and Esri can decide to merge them or not. ... View more

Now that Summary Statistics (Analysis)—ArcGIS Pro | Documentation supports concatenation, we need a tool to do the inverse.    Either Multipart To Singlepart (Data Management)—ArcGIS Pro | Documentation could be enhanced to support attributes beyond multi-part geometries. A new 'Multi-attribute to Single-attribute (Data Management)' tool could be created. The splitting tools in the Extract toolset do not address this need for several reasons.   ... View more

I am pretty sure you are out of luck, and it isn't just an Arcade limitation.  Calculate Field has to return something for each record, there is no way to tell Calculate Field to stop processing the current record and move onto the next. ... View more

Cross posted  at query - ArcGIS REST API returns no results when resultRecordCount parameter is added - GIS SE. As a comment to that question asks, are you sure the service supports pagination, which is a requirement for this option. ... View more

I agree this is a big shortcoming of Arcade.  I am hard pressed to think of another scripting language that doesn't support, at least partially, regular expressions.  ... View more

@BrandonMcAlister, I see you posted Regular Expressions in Definition Queries .  Seeing that most data sources, including file geodatabases, already include support for regular expressions; did you figure out how to get this working? ... View more

This error message means exactly what is says, i.e., there is/was another administrative process running, and you cannot have more than one administrative process executing at the same time.  That said, orphaned lock files can cause ArcGIS Server to think an administrative process is still happening when it isn't.  Check the locks folder (if you have access to the arcgissystem folder), or you could also try restarting the machine. ... View more

I can't say it is the cause of your issue, but don't mix the field name wild card while also explicitly naming fields because it results in duplicate columns in the cursor. ... View more

Regarding page file size, where did you get or see that statement?  If a server needs a page file 3x the size of its RAM, I can guarantee any applications running on it are performing quite poorly. If you are not familiar already with the concepts and information in Introduction to the page file - Windows Client | Microsoft Learn and How to determine the appropriate page file size for 64-bit versions of Windows - Windows Client | Microsoft Learn, I encourage you to read both. A page file serves multiple purposes, and even with a given purpose, the use of a page file can vary greatly.  Most of the rules of thumb were created in the early days of the Windows NT operating system when machines had much smaller amount of physical RAM, and they are far from optimal for modern servers with large quantities of RAM. In the articles I linked to, Microsoft explains how the "system managed" page file settings generally work.  Unless you want to dive into process performance data to get a better understanding of how your applications are using memory, virtual and physical, it might be best to just let Microsoft manage it. As an example, the Windows 11 Professional workstation I primary use has 64 GB of RAM and currently the system-managed page file is 3 GB, that is 1/20th the size of physical RAM.  The page file will occasionally grow by tens of GBs when I start pushing RAM consumption, but it seldom goes above 30 GB, which is still 1/2 the physical RAM.  Could I provision a 128 GB or 192 GB page file manually?  Sure, but why waste 128 GB of SSD storage on a page file that isn't used. ... View more

The SQL LIKE predicate is a form of pattern matching, but it is not regular expression pattern matching.  Although support for SQL LIKE is much more consistent across database platforms than regular expressions, there may be cases where it is implementation specific, so it is best to state what data source you are working with. UPDATE:  An update to the question indicates you are working with file geodatabase data. As I mentioned already, SQL LIKE is not regular expression, and regular expression patterns will not work with LIKE, especially since Esri does not support character-class wildcards with the file geodatabase implementation of LIKE. Although undocumented, Esri does support a fairly robust regular expression implementation in the file geodatabase with the SIMILAR TO predicate.  Oddly, they even kept the wildcard the same as LIKE even though actual regular expression uses different wildcards. ... View more