To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96883
Issue #|96883
Summary|Base not calling Sage 50 ODBC
Component|Database access
Version|OOO300m9
Platform|PC
URL|
OS/Version|Windows XP
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|none
Assigned to|msc
Reported by|brucedenney
------- Additional comments from [EMAIL PROTECTED] Thu Dec 4 10:58:36 +0000
2008 -------
I have been unable to properly use the Sage 50 ODBC drivers with Open Office,
this has been an issue for many years.
I have managed to get someone in Sage (Darron Cockram) to have a look at the
problem and he seems to think, the issue lies in Open Office.
<QUOTE>I finally had a chance to investigate this a bit further at the end of
last week and I can report that the problem lies with Open Office and
not the ODBC driver.
I built a debug version of the ODBC driver DLL, set some break points in
the code and attempted to execute the query SELECT * FROM COMPANY. Even
though the error message was given none of the break points were hit,
not even those in the ParseSQL functions. This rang some alarm bells so
I ran process monitor to see what was going on and Open Office was not
loading or using the ODBC driver DLL when the error message was given.
Turning on the 'Execute SQL Directly' option in Open Office and
re-running the tests showed that the break points in the code were hit,
that the DLL did get loaded, and more importantly that no error was
given with the expected results being returned.
The conclusion that we can draw from this is that whatever the problem
is it must be within Open Office as the ODBC driver is not being loaded
or used when the error message is given. Fortunately the fix would
appear to be simply to turn on the 'Execute SQL Directly' option in Open
Office which I believe the customer has already discovered.
Any questions just let me know.</QUOTE>
I can confirm that executing the SQL directly does work this is the way I have
been working around this for the last few years, however, cutting and pasting
from MS Query to Base is not really a solution, it is a work around.
I would really love to be able to use the Base Query Wizard and it to work
properly and I am sure that you guys want that as well.
I have seen a few other posts that seem to have similar issues with other ODBC
sources, I am wondering if there is a more generic problem here and that perhaps
solving this issue might solve some elsewhere.
------------------------------
Once drivers are installed, I created a base, using the drivers.
Opening a CAT_TITLE table returns the error.
---
The Data could not be loaded
Syntax error in expression
---
hitting More gives a list of 4 errors.
---
The data content could not be loaded.
---
SQL Status: HY000
Error code: 1000
Syntax error in SQL expression
---
SQL Status: HY000
Error code: 1000
SELECT * FROM 'CAT_TITLE'
---
SQL Status: HY000
Error code: 1000
syntax error, unexpected STRING, expecting '(' or '{' or NAME
---
Creating queries using SQL direct works, but using design view or the wizards
creates errors similar to above.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
