Write, Bureaucrats, Administrators
2,725
edits
Difference between revisions of "Troubleshooting the MYOB ODBC driver"
Jump to navigation
Jump to search
Troubleshooting the MYOB ODBC driver (view source)
Revision as of 18:01, 3 March 2014
, 18:01, 3 March 2014no edit summary
| Line 23: | Line 23: | ||
# From the '''File''' menu, select '''Verify Company File''' and wait for the process to complete; | # From the '''File''' menu, select '''Verify Company File''' and wait for the process to complete; | ||
# From the '''File''' menu, select '''Optimise Company File''' and wait for the process to complete; | # From the '''File''' menu, select '''Optimise Company File''' and wait for the process to complete; | ||
| Line 60: | Line 49: | ||
<br clear=all> | <br clear=all> | ||
== File and Folder Access Requirements == | |||
The MYOB ODBC driver requires '''Read''' and '''Write''' access to specific folders in order to function properly. This is typically a problem when running third-party software from a Terminal Server environment. In those environment, IT Administrators typically lock things down to ensure nothing breaks. As a first step, we recommend you get your IT Administrator to verify your permissions and grant you '''Full Control''' to the following locations. | |||
* The folder containing your '''MYOB data file'''; | |||
* The folder containing the '''MYOB ODBC driver''' (e.g. c:\MYOBODBCAU10\); | |||
* The folder containing the '''MYOB application''' (e.g. C:\Premier19\); | |||
* The folder containing '''BudgetLink''' (e.g. C:\BudgetLink v3.0.0.0\); | |||
* The file '''ntdll.dll''' used for the SendMessage API (e.g. C:\Winnt\System32\ntdll.dll); | |||