Dennis,
Sound like an issue on how the Windows versions interpret the relative path.
Have you tried using the full path?
If it is any help, this is what I use to connect:
SET VAR vCommandC = ('SCONNECT ' + '''' +
+';driver={SQL
Server};server=PWVSC-SHARE\SQLEXPRESS;database=FUELMASTERPLUSSQL;Trusted_Con
nection=YES;' + '''')
Javier,
Javier Valencia, PE
O: 913-829-0888
H: 913-397-9605
C: 913-915-3137
From: [email protected] [mailto:[email protected]] On Behalf Of Dennis
McGrath
Sent: Wednesday, March 27, 2013 11:25 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: SATTACHED table problem
Javier,
Both RBDOS and RBWIN (compiled) are using the same database.
This is an invoice printer app.
The DB is running with STATICDB ON. A few SQL Server Tables are permanently
SATTACHED.
It is a DSNLESS connection providing username and password
>From RBDOS I ZIP out to the compiled application, passing the order ID.
The compiled app uses the order ID to retrieve most of the data from the
RBASE database.
It then uses that data to insert the install address(es) into a temp table
from the permanently attached SQL Server table.
This works perfectly on XP or Vista.
On Windows 7 everything works, except the SQL data pull which retrieves
nothing.
I got a brainstorm.
I tried shelling out to full RBWIN from RBDOS to see if it also suffers from
the same problem.
In this session of RBWIN I tried retrieving data from the SQL Server table
and got this error:
Specified driver could not be loaded due to system error 126: The specified
module could not be found.
(SQL Server, %WINDIR%\System32\SQLSrvr32.dll).
I then tried adding WINDIR=C:\WINDOWS to my RBDOS startup batch file.
It did not help.
Dennis McGrath
Software Developer
QMI Security Solutions
1661 Glenlake Ave
Itasca IL 60143
630-980-8461
[email protected]
From: [email protected] [mailto:[email protected]] On Behalf Of Javier
Valencia
Sent: Wednesday, March 27, 2013 10:28 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: SATTACHED table problem
Dennis,
I have an application (compiled) that has a SQL Server table permanently
attached and seems to work correctly. I have utility in the compiled
application that reset the connection if somehow it gets disconnected and
displays the SQL server table data in a grid to make sure data is being
read.
Is the compiled application creating files you upload into your RBDOS
application? If this is the case, does the user of the compiled application
have the proper read/write privileges? This seem to be an issue when moving
to Windows 7 and its administrative overhead. Have you tried accessing the
compiled application using ODBC from your RBDOS application?
Maybe if you provide a little more detail on the entire procedure we can
figure out why it is not working or come up with a workaround.
Javier,
Javier Valencia, PE
O: 913-829-0888
H: 913-397-9605
C: 913-915-3137
From: [email protected] [mailto:[email protected]] On Behalf Of Dennis
McGrath
Sent: Wednesday, March 27, 2013 8:55 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - SATTACHED table problem
We have a permanently SATTACHed SQL Server table (DSNLESS).
We have our RBDOS app ZIP out to run a compiled app that uses this data.
This worked great until we started using Windows 7.
The compiled app still works, EXCEPT when we ZIP to it from RBDOS.
When we do that, everything works EXCEPT pulling data from the SQL Server
table.
Has anyone else encountered anything like this?
Blues clues?
Dennis McGrath
Software Developer
QMI Security Solutions
1661 Glenlake Ave
Itasca IL 60143
630-980-8461
[email protected]
