Home
> Uncategorized > Connection string for Sage ODBC via OLEDB
Connection string for Sage ODBC via OLEDB
Provider=MSDASQL.1;Persist Security Info=False;User ID=Manager;Data Source=SageLine50v9;Extended Properties="DSN=SageLine50v9;UID="
When Sage Line 50 is installed, it creates a system ODBC DSN called SageLine50v9 (I assume other versions of sage have corresponding names). The "database "contains the following tables:
TABLES |
COMPANY |
PERIOD |
SALES_LEDGER |
PURCHASE_LEDGER |
NOMINAL_LEDGER |
AUDIT_HEADER |
AUDIT_SPLIT |
AUDIT_JOURNAL |
AUDIT_VAT |
AUDIT_USAGE |
DEPARTMENT |
BANK |
STOCK |
STOCK_TRAN |
STOCK_CAT |
STOCK_COMP |
INVOICE |
SALES_ORDER |
PURCHASE_ORDER |
RECURRING |
FIXED_ASSET |
FIXED_ASSET_CAT |
PREPAYMENT |
ACCRUAL |
INVOICE_ITEM |
SOP_ITEM |
POP_ITEM |
SALES_CONTACT |
PURCHASE_CONTACT |
SALES_DEL_ADDR |
PURCHASE_DEL_ADDR |
COMPANY_DEL_ADDR |
PRICE |
PRICE_LIST |
GRN_ITEM |
CHART_LIST |
CAT_TITLE |
CATEGORY |
TAX_CODE |
UPDATE_LEDGER |
CURRENCY |
VAT_SUMMARY |
VAT_RETURN |
REMITTANCE |
Categories: Uncategorized
Hi, this is interesting but how did you get the connection string for Sage, cause I’m dealing with Intégrale and it’s not the same connection string. If you can help, thanks for posting.
LikeLike
Hi Waly DIOUF, Make sure you install the ODBC Driver for the version of SAGE you have.
LikeLike
I am Integrate Sage to our windows application. But I am facing problem for select company in 2011 version.
szDataPath = oSDO.SelectCompany(“C:\\Documents and Settings\\All Users\\Application Data\\Sage\\Accounts\\2011\\IREPractice\\AcctDATA\\ACCOUNT.DTA”);
it shows a window but no any company. How to solve this problem.
LikeLike
I am trying to connection SAGE line 50 version 21 to c# and it is giving me error Provider=MSDASQL.1;Persist Security Info=False;User ID=Manager;Data Source=SageLine50v9;Extended Properties=”DSN=SageLine50v9;UID=”
LikeLike
I am trying to connection SAGE line 50 version 21 to c# and it is giving me error ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
LikeLike