27-08-2011 06:15 PM
Hi All,
I need a help in finding the correct software which can provide with 'Write Access' permissions to the MYOB files.
I downloaded the trial version of ODBC Direct driver for Windows for this (only for testing in Windows environment), have created the system DSN after this and then later on write a PHP script to connect using the ODBC connectivity. The script for reading data is working fine. But 'Writing into MYOB database tables' does not allowed using the script.
All I help for the following queries :-
1) Which driver I need to use for insert data into MYOB database. Can MYOB ODBC direct solve this purpose.
2) MYOB files exists at VPN, so do I need to purchase linux driver for this? Please let me know which driver should I purchase for linux environment and where can I request for buying this software?
Solved! Go to Solution.
28-08-2011 02:39 PM
The ODBC driver is a read-write driver. A license for Write access is either purchased by your client, or provided by developers registered to the MYOB developer program, who either provide it to the client as part of their app, or charge for it separately. For details about this program contact developers@myob.com.
The ODBC driver is for Windows platform only. If you can already read the database, nothing else is required to write except as above.
21-10-2011 09:26 PM
Hey,
I am getting error
Warning: odbc_execute() [function.odbc-execute]: SQL error: [MYOB ODBC]Cannot execute an INSERT IN read-only mode., SQL state 08004 in SQLExecute in odbcfile.php
Please help me in solving this ASAP.
Thanks
22-10-2011 06:23 AM
According to the error message you are in read only mode but you are attempting to execute a write statement.
Regards,
Taz
22-10-2011 02:31 PM
Hi
You do not have a write version of the ODBC driver - the version you have is read only. You need to become a MYOB Developer Partner to gain access to the Read/Write driver as the unlocking of the ODBC driver through MYOB only provides the read only version.
Regards
Clive Williams
24-10-2011 03:54 PM
Thanks for the reply.
Let me know please if I can test the writing into MYOB first without having the developer access?
And how can I apply to be a developer partner and what about the pricing plans for the same?
Thanks
25-10-2011 09:05 AM
Hi
http://myob.com.au/partners/become-a-partner/devel
Regards
Clive Williams
25-10-2011 03:30 PM
Hi Guys,
As Clive mentioned you will need to become a partner to have full read-write access to the ODBC drivers using live files.
You can test the write back function using the clearwater sample file that comes with your AccountRight.
Would you like to show your appreciation?
-----Give KUDOS!
Has someone answered your post?
-----Make it an ACCEPTED SOLUTION!
08-02-2012 01:00 AM
Hi Guys,
I am trying to make a insert data to MYOB using simple java utility. I can read data easily from MYOB but while writing data to MyOb prompt for entering credentials comes program terminates showing below exception
**********Environment Variables *********
OPENRDA_INI = <NOT_SET>
PATH = <C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System3
gram Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\WINDOWS\syst
LD_LIBRARY_PATH = <NOT_SET>
SHLIB_PATH = <NOT_SET>
CLASSPATH = <;SAAECommIntegrationMYOB-1.0.0.jar;SAAECommIntegr
.jar;SAAECommIntegrationCore-1.0.0.jar;;SAAECommIn
ECommIntegrationMYOB-1.0.0.jar;SAAECommIntegration
grationCore-1.0.0.jar;;SAAECommIntegrationMYOB-1.0
YOB-1.0.0.jar;SAAECommIntegrationCore>
ODBCINI = <NOT_SET>
**************************************************
CLI : [TID: 105C]:[Tue Feb 07 19:05:30.741 2012] rdacstmt.c:99: *** rda_cliAllocStmt: connection is not opened
SQLD: [TID: 105C]:[Tue Feb 07 19:05:40.304 2012] damdrv.c:881: sqldrv_commit(): IP endTransaction() returned error.
SQLS: [TID: 105C]:[Tue Feb 07 19:05:40.304 2012] sqlserv.c:501: *** sqls_commit: Unable to commit transaction.
CLI : [TID: 105C]:[Tue Feb 07 19:05:40.304 2012] rdacevnt.c:1256: *** procComitCnf: SQL_COMMIT caused a rollback. Error = 10181
CLI : [TID: 105C]:[Tue Feb 07 19:05:40.304 2012] rdacutl.c:831: *** RDA_cliCommit: can't execute R-Commit
SQLD: [TID: 105C]:[Tue Feb 07 19:05:48.725 2012] damdrv.c:881: sqldrv_commit(): IP endTransaction() returned error.
SQLS: [TID: 105C]:[Tue Feb 07 19:05:48.725 2012] sqlserv.c:501: *** sqls_commit: Unable to commit transaction.
CLI : [TID: 105C]:[Tue Feb 07 19:05:48.725 2012] rdacevnt.c:1256: *** procComitCnf: SQL_COMMIT caused a rollback. Error = 10181
CLI : [TID: 105C]:[Tue Feb 07 19:05:48.725 2012] rdacutl.c:831: *** RDA_cliCommit: can't execute R-Commit
SQLD: [TID: 105C]:[Tue Feb 07 19:05:57.132 2012] damdrv.c:881: sqldrv_commit(): IP endTransaction() returned error.
SQLS: [TID: 105C]:[Tue Feb 07 19:05:57.132 2012] sqlserv.c:501: *** sqls_commit: Unable to commit transaction.
CLI : [TID: 105C]:[Tue Feb 07 19:05:57.132 2012] rdacevnt.c:1256: *** procComitCnf: SQL_COMMIT caused a rollback. Error = 10181
CLI : [TID: 105C]:[Tue Feb 07 19:05:57.132 2012] rdacutl.c:831: *** RDA_cliCommit: can't execute R-Commit
SQLD: [TID: 105C]:[Tue Feb 07 19:06:05.569 2012] damdrv.c:881: sqldrv_commit(): IP endTransaction() returned error.
SQLS: [TID: 105C]:[Tue Feb 07 19:06:05.569 2012] sqlserv.c:501: *** sqls_commit: Unable to commit transaction.
CLI : [TID: 105C]:[Tue Feb 07 19:06:05.569 2012] rdacevnt.c:1256: *** procComitCnf: SQL_COMMIT caused a rollback. Error = 10181
CLI : [TID: 105C]:[Tue Feb 07 19:06:05.569 2012] rdacutl.c:831: *** RDA_cliCommit: can't execute R-Commit
SQLD: [TID: 105C]:[Tue Feb 07 19:06:14.007 2012] damdrv.c:881: sqldrv_commit(): IP endTransaction() returned error.
SQLS: [TID: 105C]:[Tue Feb 07 19:06:14.007 2012] sqlserv.c:501: *** sqls_commit: Unable to commit transaction.
CLI : [TID: 105C]:[Tue Feb 07 19:06:14.007 2012] rdacevnt.c:1256: *** procComitCnf: SQL_COMMIT caused a rollback. Error = 10181
CLI : [TID: 105C]:[Tue Feb 07 19:06:14.007 2012] rdacutl.c:831: *** RDA_cliCommit: can't execute R-Commit
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x77e4bef7, pid=1084, tid=4188
#
# JRE version: 6.0_30-b12
# Java VM: Java HotSpot(TM) Client VM (20.5-b03 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [kernel32.dll+0xbef7]
#
# An error report file with more information is saved as:
# C:\DOCUME~1\ankitk\LOCALS~1\Temp\2\hs_err_pid1084.
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
CLI : [TID: 105C]:[Tue Feb 07 19:06:44.022 2012] rdachenv.c:342: rda_cliFreeEnv() 1 connection handles still exist under this environment handle
[error occurred during error reporting , id 0xe06d7363]
--------------------------------------------------
Some times I get below exception.
java.sql.SQLException: [MYOB ODBC] - Cannot determine if MYOB was AutoStarted
at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source)
It seems that connection is not closed to MyOB file but I have manually closed all the connection.
How can I verify that record is inserted properly in myOB database.Because import tables are read only.
I have read in user guide that
Information is committed by importing it from the import tables into an AccountRight
company file.
But I do not know how to import tables to AcountRight company file.
Has any done inserted record to MYOB database using java,please let me know.
Any help would be apreciated.
Thanks,
Ankit
10-02-2012 02:21 PM
Hi Ankit,
As mentioned in the above posts to have full read/write access to the ODBC Driver you will need to become an MYOB Developer Partner. Details on becoming a Partner can be found at http://myob.com.au/partners/become-a-partner/devel
Would you like to show your appreciation?
----- Give KUDOS!
Has someone answered your post?
-----Make it an ACCEPTED SOLUTION!
