Microsoft Visual Basic Unexpected Error 50001 Mac

Microsoft Visual Basic Unexpected Error 50001 Mac
  1. Sql Error 50001

(This issue does not apply to Mac) A method or property cannot be used because of security settings. For example, the properties and methods of the VBE object for manipulating the Visual Basic for Applications (VBA) code that is stored in a Microsoft Office document are inaccessible by default. Try to open the affected file. If the affected file is still inaccessible then apply the below-given trick: Click on the Start button Open run dialogue box and type. “C: Program Files Microsoft Office Office excel.exe” /s. After it, try to open the file again.


  1. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container. Microsoft Visual Studio VC Package 1.0 Microsoft Visual Studio VC Package Mono Debugging for Visual Studio 4.8.4-pre (3fe64e3) Support for debugging Mono processes with Visual Studio.
  2. This seems to be related to producing PDB files? This has hit me as well, although this occurs without the use of visual-studio-mac (it's a problem with xbuild, I only experience this on one project, a web/ project which builds on Windows fine, and then hosts on Mac fine, but doesn't build on mac.) – Shaun Wilson Nov 16 '16 at 19:12.
  3. Excel Error 50001 Memory Leak - Error 50001 memory leak results in Microsoft Excel continually using more and more memory, bogging down the system. Possible causes include failure of Microsoft Corporation to de-allocate memory in the program, or when bad code is executing an 'infinite loop'.

Run-time error '-2147217900 (80040e14)':[Microsoft][ODBC SQL Server Driver][SQL Server]The query uses non-ANSI outer join operators ('*=' or '=*').
To run this query without modification, please set the compatibility level for current database to 80 or lower, using stored procedure sp_dbcmptlevel. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN).
In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes
This error occurs in any one of the following three instances:

  1. FDM 6.0 and 7.0 - Error in GL Zoom in row format against SQL 2005 database.

  2. FRL13, FDM 6.0 and 7.0 - Error launching Report Wizard against a SQL 2005 DB.

  3. Reports with Reference Codes, TREF, TPROJ receive error against SQL 2005 DB.


This SMR has been fixed in R07670 Service Pack and subsequent Service Packs, please check or website ( for availability of Service Packs for your General Ledger. You may also sign up for automatic notification of Services on our website .


To work around the issue, do the following to set the Compatibility Level of the Database to 80:

  1. In Enterprise Manager, right click the database. Select Properties.

  2. Select the Options Tab.

  3. Change the Compatibility Level to 80.

Sql Error 50001


Comments are closed.