Gupta Report Builder / MS SQL Server

[MacDaddy]

Good afternoon,

I'm trying to use Gupta report builder 4.0 which came with out mainframe system (Infor Visual Manufacturing) to create paperwork and prints from the system.

However, I seem to have hit a snag. The DB for Infor is hoster by SQL Server 2008 but when I try to define the query for the new report I can't select SQL Server as a datasource, I don't get any further than the Source tab on the Define Query applet.



I found the Gupta Connectivity Administrator and have opened up ODBC connections; since doing this I can now see ODBC datasources from the above applet. However, I can't see anywhere in the connectivity administrator to open up/select/create SQL Server connections, my only choices are ODBC, Oracle or SQLBase.



I've looked through all sorts of .ini files to find where I'm going wrong but have come up with nothing.

How do I set up SQL Server as a datasource for creating reports in Gupta?

Thanks,

Paul

[FRBhote]

Can you post your SQL.INI file here please?

[MacDaddy]

Certianly:

; Win32
;--------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlws32 REMOTE database using TCP/IP (WinSock)
;
[win32client]
clientname=Win32Client
;clientruntimedir="C:\Program Files\Gupta\SQLBase901"

[win32client.dll]
comdll=sqlws32

[win32client.apipe]
;autostartserverpath="C:\Program Files\Gupta\SQLBase901\dbntsrv.exe"
;serverpath=instal

[win32client.ws32]
;serverpath=SERVER1,<insert database engine name here>,<insert port id here - default 2155>/*
serverpath=SERVER2,localhost,2155/island,vmfgdemo,vpaydemo,VPB


[odbcrtr]
;remotedbname=<database name>,dsn=<dsn name>
;remotedbname=vqdemo,dsn=vqdemo

[sqlserver]
NHDB=SRV-01,NHDB
NHSIM=SRVTEST-01,NHSIM
TestDB=SRV-01,TestDB
NHLIVE=SRVTEST-01,NHLIVE
FMDB=SVR-01,FMDB
NHCURRENT=SRVTEST-01,NHCURRENT

With thanks,

Paul

[FRBhote]

We connect via ODBC to Sqlserver and you can try it too. Create a DSN and change the sql.ini to:

Code: Select all

[odbcrtr]
remotedbname=NHCURRENT,DSN=NHCURRENT

[MacDaddy]

Thank you, that seems to have a measure of success, however, I now have a repetitive error that the select buffer is too small.

I have searched though other threads and this doesn't seem to be an uncommon occurrence.

Is it correct that I will be required to upgrade my version of report builder to fix this new error as suggested in this thread, or have I got this bassackwards?
https://support.guptatechnologies.com/su ... ffer#p5940

Regards,

Paul

[FRBhote]

Try this? It's what I use.

Code: Select all

remotedbname=NHCURRENT,DSN=NHCURRENT
longbuffer=20000
autocommit=off
odbctrace=off
odbctracefile=sql.log
enablemultipleconnections=off
fetchrow=255

[MacDaddy]

I really appreciate your help but it's still not working.

I'm also getting memory write errors after this latest modification, too.

Just to make sure it wan't the machine I'm using I tried it on another and that too has the same errors; select buffer too small followed by a memory write error and a crash.

Thanks all the same, though, much appreciated.

Paul

[FRBhote]

Chapter 4 of ccod.pdf:

Code: Select all

SQL.INI keywords
This section contains the keywords you need or might want to use in the SQL.INI file
when connecting a Centura SQLWindows application to Microsoft SQL Server 6.5
and 7.0.
buffrow
Use this keyword to control the buffering of data between your Centura
SQLWindows application and Microsoft SQL Server.
Section [odbcrtr]
Default 0
Syntax buffrow=number_of_rows
Description This keyword controls the buffering of data between your Centura SQLWindows
application and Microsoft SQL Server. By decreasing the buffrow value, response
time can be improved significantly. In contrast, larger values increase data
throughput, but lengthen the response time.
The values for buffrow can range from 0 through 32767. Assigning a value does not
guarantee that the current INMESSAGE is of sufficient size to fulfill the request. In
these cases, the number of buffered rows may be considerably less.
Chapter 4 Connecting to Microsoft SQL Server
4-8 Connecting Centura Objects to Databases
The default value of zero causes Microsoft SQL Server to revert to buffering data
based on the number of rows which will fit within the current INMESSAGE buffer
size.
Example This statement instructs Microsoft SQL Server to perform single row fetches into the
INMESSAGE buffer:
buffrow=1
Notes The buffrow keyword has no effect on the manner in which data is buffered and
transported across the network.
You can also configure the buffering of data for individual SQL handles using the
SqlSetParameterAll function. Assuming nBuffrow has already been assigned the
value desired for SQL handle hSql, you can make the following call:
SqlSetParameterAll(hSql,DBP_BUFFROW,nBuffRow,FALSE,TRUE)