on 2011 Jan 25 7:37 AM
Hello,
we're on the way to roll out SAPGUI 7.20 PL4. Now I discoverd a serious bug: Local input history isn't working anymore.
I switched on tracing on SAPGUI to see whats wrong, an the cause is simple: SAPGUI uses comma (,) instead of dot (.) in the generated SQL command for the local MicrosoftJet Database engine. So here is a excerpt from the trace log:
Local DB: CSapHistoryDb::GetHistoryList: SO_VBELN-LOW
Local DB(Error): CSapHistoryDb::GetHistoryList: Microsoft JET Database Engine Syntaxfehler (Komma) in Abfrageausdruck '(HistFieldname = "SO_VBELN-LOW") AND (HistTime >= 40478,353102)'.
Local DB(Error): CSapHistoryDb::GetHistoryList: Microsoft JET Database Engine Syntaxfehler (Komma) in Abfrageausdruck '(HistFieldname = "SO_VBELN-LOW") AND (HistTime >= 40478,353102)'
So, I know the bug, I know the case. Whats next step? Is the bug already known to SAP and fixed in the next release or should I open an support case?
Walter
Hi,
I had this Problem after installing Adobe Reader X (10). After viewing a PDF, the History was gone until I restarted the SAPGUI.
Btw I am from Germany too. I got this Note as Solution from SAP Support:
https://service.sap.com/sap/support/notes/867131
###
If the registry value "UseDot" is set to 1 under the path:
HKEY_CURRENT_USER\Software\SAP\SAPGUI front\SAP Frontend Server\LocalData, the comma symbol in SQL statement will be replaced with the dot. This should prevent the SQL execution error.
###
It is an old note, but it worked.
Volker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.