It had to be 32 bit FME
See : https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/arcpadaxf/arcpadaxf.htm
EDIT - Not a suitable method (see below)
Thanks Mark for your reply. I think this may be one of those things where we need to push our vendor to update the file format instead of building workarounds. We are running Windows 10, 64-bit FME, SQL Server 2016, etc. which might be a challenge.
As a side note, I did find a little program called CompactView that was helpful in looking at the database and exporting the schema and data into our modern SQL Server.
Thanks Mark for your reply. I think this may be one of those things where we need to push our vendor to update the file format instead of building workarounds. We are running Windows 10, 64-bit FME, SQL Server 2016, etc. which might be a challenge.
As a side note, I did find a little program called CompactView that was helpful in looking at the database and exporting the schema and data into our modern SQL Server.
Yes used CompactView also but just viewing tabular data, not spatial data.
Hi @kddunn Have just been looking at the Esri ArcPad AXF format with FME, and it actually ONLY reads spatial data tables despite there being non-spatial tables existing in the same database. Therefore no good for you.
Another possibility is to connect to the SQLServer CE database using Python, but that doesn't really help answer your question however.
@mark_1spatial and @kddunn
I needed to extract data from an AXF file following a major disaster on the surveyor's ArcPad device. I was disappointed to find the AXF Reader greyed out in FME but there was a message to say SQL Server Compact Edition 3.1 was required. So I went looking for that and found it in "Microsoft SQL Server 2005 Compact Edition Developer Software Development Kit". Installing that didn't work but I found "SQLServerCE31-EN.msi" in the "v3.1\\SDK\\bin\\Desktop" folder which the SDK install created.
Installing that did the trick and I was able to read the AXF. All of this though was in 32-bit FME 2016.1 on Windows Server 2008 R2 Standard, which is actually our old FME machine that's about to be switched off. Our new FME machine is Windows Server 2012 R2 Datacenter and I get a "compatibility issues" warning on that when I try to install SQLServerCE31-EN.msi. Windows couldn't tell me what the issues were so I'm not sure if it would work or not. I've used the old machine for this one off task to be sure of getting a result.
Will Safe stop claiming support for AXF if newer operating systems make the Reader unusable because you can't install SQL Server Compact Edition? Or will a new Reader be issued? Otherwise the claim to support 400+ formats starts to just a little bit shaky!
@mark_1spatial and @kddunn
I needed to extract data from an AXF file following a major disaster on the surveyor's ArcPad device. I was disappointed to find the AXF Reader greyed out in FME but there was a message to say SQL Server Compact Edition 3.1 was required. So I went looking for that and found it in "Microsoft SQL Server 2005 Compact Edition Developer Software Development Kit". Installing that didn't work but I found "SQLServerCE31-EN.msi" in the "v3.1\\SDK\\bin\\Desktop" folder which the SDK install created.
Installing that did the trick and I was able to read the AXF. All of this though was in 32-bit FME 2016.1 on Windows Server 2008 R2 Standard, which is actually our old FME machine that's about to be switched off. Our new FME machine is Windows Server 2012 R2 Datacenter and I get a "compatibility issues" warning on that when I try to install SQLServerCE31-EN.msi. Windows couldn't tell me what the issues were so I'm not sure if it would work or not. I've used the old machine for this one off task to be sure of getting a result.
Will Safe stop claiming support for AXF if newer operating systems make the Reader unusable because you can't install SQL Server Compact Edition? Or will a new Reader be issued? Otherwise the claim to support 400+ formats starts to just a little bit shaky!