Hello
I'm pulling my hair out trying to make a simple ASP page that connects to my Sage Timberline Office Accounting & Property Management data. There have been some other posts, but none of those really describe my problem much.
I run Timberline on a Windows 2000 Server with SP4. We're on 9.2.1. I gave up trying to access the data from my real web server, so I installed IIS on the TL server for simplicity's sake. I run task security, and my special DSN user has unlimited rights. We don't do file security, but I checked anyway to make sure my tables were clear. My Timberline Data ODBC driver in odbcad32.exe is 9.02.55.20.
Most of the Connection Strings listed in other posts work to establish the connection. The problem I have is that the connection only brings back the COMPANY_INFORMATION table (I use the OpenSchema(20) method to loop the tables, and that's the only one that comes back.) Since none of the useful tables are present, my Recordset doesn't connect, creating either a "-Microsoft OLE DB Provider for ODBC Drivers (0x80040E37) [TimberlineODBC][TimberlineODBCEngine ODBC Driver][DRM File Library]No such table or object.-" or "-Microsoft VBScript runtime (0x800A01FB) An exception occurred: 'Open'-" error on the Recordset open.
I've tried messing with the table descriptions & max segment size in the DSN to no avail. I’ve tried using the standard names for the Tenant table I’m looking up. I've tried using the DNS-less Connectionstring with the same problem. I don't think using the Pervasive driver will work the way it will for Service Management, because of the way Timberline has its data files. (I can connect to SM just fine.)
This is what I have so far:
<%
Set cnTL = server.CreateObject("ADODB.Connection")
Set rsTL = Server.CreateObject("ADODB.Recordset")
dim sConnString, rsX0
sConnString = "DSN=TL-GCG;Uid=dsn;Pwd=dsn;CODEPAGE=1252;DictionaryMode=false;StandardMode=true"
cnTL.Open sConnString
‘^^ this part seems to work fine
rsX0 = "SELECT * FROM TENANT_PMN_TENANT"
rsTL.Open rsX0, cnTL
'^^ no soup for you! errors!
%>
Despite nearly nine grand a year for our support contract, Timberline’s support has failed to get results, because they don’t support ODBC functions beyond Word, Access, and Excel. Sage Timberline Office is the bane of my existence.
Any ideas? Thanks.
I'm pulling my hair out trying to make a simple ASP page that connects to my Sage Timberline Office Accounting & Property Management data. There have been some other posts, but none of those really describe my problem much.
I run Timberline on a Windows 2000 Server with SP4. We're on 9.2.1. I gave up trying to access the data from my real web server, so I installed IIS on the TL server for simplicity's sake. I run task security, and my special DSN user has unlimited rights. We don't do file security, but I checked anyway to make sure my tables were clear. My Timberline Data ODBC driver in odbcad32.exe is 9.02.55.20.
Most of the Connection Strings listed in other posts work to establish the connection. The problem I have is that the connection only brings back the COMPANY_INFORMATION table (I use the OpenSchema(20) method to loop the tables, and that's the only one that comes back.) Since none of the useful tables are present, my Recordset doesn't connect, creating either a "-Microsoft OLE DB Provider for ODBC Drivers (0x80040E37) [TimberlineODBC][TimberlineODBCEngine ODBC Driver][DRM File Library]No such table or object.-" or "-Microsoft VBScript runtime (0x800A01FB) An exception occurred: 'Open'-" error on the Recordset open.
I've tried messing with the table descriptions & max segment size in the DSN to no avail. I’ve tried using the standard names for the Tenant table I’m looking up. I've tried using the DNS-less Connectionstring with the same problem. I don't think using the Pervasive driver will work the way it will for Service Management, because of the way Timberline has its data files. (I can connect to SM just fine.)
This is what I have so far:
<%
Set cnTL = server.CreateObject("ADODB.Connection")
Set rsTL = Server.CreateObject("ADODB.Recordset")
dim sConnString, rsX0
sConnString = "DSN=TL-GCG;Uid=dsn;Pwd=dsn;CODEPAGE=1252;DictionaryMode=false;StandardMode=true"
cnTL.Open sConnString
‘^^ this part seems to work fine
rsX0 = "SELECT * FROM TENANT_PMN_TENANT"
rsTL.Open rsX0, cnTL
'^^ no soup for you! errors!
%>
Despite nearly nine grand a year for our support contract, Timberline’s support has failed to get results, because they don’t support ODBC functions beyond Word, Access, and Excel. Sage Timberline Office is the bane of my existence.
Any ideas? Thanks.