Post Upgrade, Client tools (Deski & Webi) are using US date format (MM/DD/YYYY). This is causing issues as users are earlier used to enter/view dates in UK date format (DD/MM/YYYY). We have updated regional settings on users machine to make sure it is UK format. Still in client tools it is not reflecting. How to resolve this?
Related
Am using MS Access 2016 to develop an application managing images. But some of my users are still using MS Access 2007 on their computers. And the receive the error "unrecognized database format".
So I would like to know if there is any solution for this. Like making my application compatible for previous versions.
I did some researches for days but not satisfied yet.
Need any help, solution or advice please. Thanks
Develop using the lowest version that your application will address, here 2007.
A newer version - 2010 and onwards - will run an older with no problems. However, 2007 is 32-bit only, thus - if you use API calls and some users run Access 64-bit - you must take care of that.
I am having a problem replicating a SQL server database. I am using a transactional replication and just finished creating my local publication when i receive this error while the snapshot agent was running:
A .NET Framework error occurred during execution of user-defined
routine or aggregate "sp_scriptdropinsreconciliationproc_sqlclr":
System.Data.SqlClient.SqlException: The locale identifier (LCID) 1072
is not supported by SQL
Can someone please help me with this situation? thanks & much appreciated.
So solving this issue was simple.i had the wrong windows locale language pack selected when SQL server was installed the first time .Steps i took:
uninstall SQL server.
changed locale ID to its appropriate selection (South African to USA Locale as SQL Server did not recognize my locale ID "soto" (South Africa). ).
re-installed SQL Server on the new locale ID.
Replication works.
Great Success.
So Tanner was right but i wanted to provide a clearer answer to those who might experience this problem in future.
I've recently migrated my Ektron installation (8.01 SP1) to a new server which had the regional settings as US (ran the installers, moved database and restored).
I changed the region to UK and restored the database (a backup from a server which was region UK).
However when a user selects a date (say publication date metadata) using the date picker , it's displayed as UK but saved in US format.
What configuration change do I need to do to fix this?
I've fixed the issue. I looked at which users were running the Ektron services (local user) and SQL Express (Network services).
I then applied the UK regional settings to the system accounts by following these instructions
http://windows.microsoft.com/en-gb/windows-vista/apply-regional-and-language-settings-to-reserved-accounts
Did a reboot and the dates are in the correct format.
ESRI suggests not to use SDO_Georaster data type on Orcle 11g R2 for the following reson:
http://support.esri.com/en/knowledgebase/techarticles/detail/38940
We had ArcGIS 10.1 setup on Oracle 11g R2 and we are able to insert data into SDO_GEORASTER data type.
Is there anyone that experienced that bug¸or was able to reproduce it ?
it looks like no body talks about it on the web! I must be missing something here :/
Is it really a bug ?
It looks like I've solved the problem...
We are now able to insert data into SDO_GEORASTER without any problem using Oracle 11g R2 using the following geoprocessing tool:
Data Management Tools => Raster => Raster Dataset => Copy Raster
The regionnal settings of my ArcGIS Desktop computer was French Canadian. So ArcGIS was inserting comas as decimal separators in the raster metadata.
I've found this by using the following to SQL commands:
SDO_GEOR.validateGeoRaster() and SDO_GEOR.schemaValidate()
Last night ESRI support team that was helping me confirmed that Regional settings would be to workaround for this bug:
Regarding the Oracle bug, it actually looks like Oracle has not adequately updated their bug database. Upon further investigation on our bug (NIM069549) that references the Oracle bug, there is an activity logged by one of the Esri Inc support staff. He mentions that he spoke to Oracle in May 2012, and that Oracle has actually closed this Oracle incident (12537431) as NOT a bug. This analyst says that the reason given is because OCIEnvNlsCreate uses the national language setting of the computer (Nls = National Language Setting). OCIEnvNlsCreate is used when creating an sdo_georaster and the failure occurs when the Oracle xml document is created.
Basically – the reason that users can experience this Oracle bug is
because of regional language settings in either the O/S or Oracle.
We have spoken to Esri Inc and have requested that the following be
updated to reflect this finding from Oracle:
NIM069549 - http://support.esri.com/en/bugs/nimbus/TklNMDY5NTQ5 NOTE:
have requested that the alternate solution be changed to state that it
can be caused by regional language settings. Also, reason for
rejection needs to be changed accordingly
Error: An Oracle LPX-0019 error occurs when inserting data into an
SDO_GEORASTER field
-http://support.esri.com/en/knowledgebase/techarticles/detail/38940 NOTE: have requested that the solution/workaround be changed to state
that it can be caused by regional language settings. Suggested to try
changing to English language setting.
ArcGIS and the Oracle Spatial raster type -
http://resources.arcgis.com/en/help/main/10.1/index.html#//002n0000006z000000
NOTE: this is the article with the known limitations at the bottom.
Since metadata is in XML format, it is quite possible that the commas
you were getting with the French language setting were directly
related to this issue. The Oracle XmlLoadDom function returns the
erorr, so you will see this error in Oracle, not in ArcMap.
I created an application using MS Access 2007 that utilizes Date pickers (among other functionalities). I then saved it as Access 2003 db, but I was reported that date pickers aren't working.
Now, I'm changing other issues I found there, but I read somewhere (google search) that MS Access doesn't support Date pickers, and that one must install something additionally in order to support date pickers. If this isn't an option, do I have any other way of enabling date pickers?
Thank you
Another approach is to use Stephen Lebans' date picker. I've used it and it works fine, though it is somewhat old-fashioned-looking.
You need to distribute the date picker control with the .mdb file