Problem deploying DBX4 - stored procedure parameter error

[pete welch]

When deploying an application that makes a stored procedure
call to SQL2K using dbEpress, an error pops up complaining
about one of the stored procedure parameters. However, if I run
the application from my development box, there are no
complaints and it works fine.

I add the file dbxmss30.dll to the deployed exe directory. I
didn't do anything like run regsvr32 on it. The DBX
documentation has few examples, so I have no idea what else
might be needed. Do I need to install some sort of SQL Server client in addition to the dbxmss30.dll?

Another question is, is there a standard way to provide
authentication for a Windows-only Authentication mode in SQL2K
(assuming multiple pc-based clients that call a stored procedure on the SQL Server)? My notion is to grant
Domain/Users access to the stored procedure since the SQL
server and the clients are all on the same domain. But, what do
I use for user and password in SQLConnection.Params? Maybe,
nothing -- leave them blank. There is another parameter in the
Params property of TSQLConnection called OS Authentication that
suggests a value of True or False. Can't find any documentation
on it but I guess it should be True.

I will be grateful for any ideas or related discussion.

Pete

[Esteban Pacheco]

Hello,

I had the same problem, I couldnt find a real solution to it. The only way
I was able to make it work on production was by adding the 2 dbx .ini files
that controlled the supported connections on the same directory as my
executable.

You can look for a previous post where I went through a big troubleshooting
without any positive results.

Let me know how it works for you.

Att.
Esteban Pacheco

Post by pete welch
When deploying an application that makes a stored procedure
call to SQL2K using dbEpress, an error pops up complaining
about one of the stored procedure parameters. However, if I run
the application from my development box, there are no
complaints and it works fine.
I add the file dbxmss30.dll to the deployed exe directory. I
didn't do anything like run regsvr32 on it. The DBX
documentation has few examples, so I have no idea what else
might be needed. Do I need to install some sort of SQL Server client in
addition to the dbxmss30.dll?
Another question is, is there a standard way to provide
authentication for a Windows-only Authentication mode in SQL2K
(assuming multiple pc-based clients that call a stored procedure on the
SQL Server)? My notion is to grant
Domain/Users access to the stored procedure since the SQL
server and the clients are all on the same domain. But, what do
I use for user and password in SQLConnection.Params? Maybe,
nothing -- leave them blank. There is another parameter in the
Params property of TSQLConnection called OS Authentication that
suggests a value of True or False. Can't find any documentation
on it but I guess it should be True.
I will be grateful for any ideas or related discussion.
Pete

[pete welch]

Esteban,

I'm ever so grateful for your post. You were absolutely
correct. Merely creating a new connection name in the
dbxconnections.ini file from the TSQLConnections Editor and
adding it to the exe directory did the trick (didn't need the
other ini file). I didn't take the time to inspect the
difference but the default MSSQLConnection name has fewer
parameters. By creating a new Connection of type MSSQL, I see
much more detail. I had to change the %.dbo to sa.dbo for it
to pass the Test Connection button.

My impression is that the default MSSQL connection is
incomplete and so we are required to create a new named
connection.

Post by Esteban Pacheco
Hello,
I had the same problem, I couldnt find a real solution to it. The only way
I was able to make it work on production was by adding the 2 dbx .ini files
that controlled the supported connections on the same directory as my
executable.
You can look for a previous post where I went through a big troubleshooting
without any positive results.
Let me know how it works for you.
Att.
Esteban Pacheco

Post by pete welch
When deploying an application that makes a stored procedure
call to SQL2K using dbEpress, an error pops up complaining
about one of the stored procedure parameters. However, if I run
the application from my development box, there are no
complaints and it works fine.
I add the file dbxmss30.dll to the deployed exe directory. I
didn't do anything like run regsvr32 on it. The DBX
documentation has few examples, so I have no idea what else
might be needed. Do I need to install some sort of SQL Server client in
addition to the dbxmss30.dll?
Another question is, is there a standard way to provide
authentication for a Windows-only Authentication mode in SQL2K
(assuming multiple pc-based clients that call a stored procedure on the
SQL Server)? My notion is to grant
Domain/Users access to the stored procedure since the SQL
server and the clients are all on the same domain. But, what do
I use for user and password in SQLConnection.Params? Maybe,
nothing -- leave them blank. There is another parameter in the
Params property of TSQLConnection called OS Authentication that
suggests a value of True or False. Can't find any documentation
on it but I guess it should be True.
I will be grateful for any ideas or related discussion.
Pete

[pete welch]

Esteban,

I'm ever so grateful for your post. You were absolutely correct. Merely creating a new connection name in the dbxconnections.ini file from the TSQLConnections Editor and adding it to the exe directory did the trick (didn't need the other ini file). I didn't take the time to inspect the difference but the default MSSQLConnection name has fewer parameters. By creating a new Connection of type MSSQL, I see much more detail. I had to change the %.dbo to sa.dbo for it to pass the Test Connection button. My impression is that the default MSSQL connection is incomplete and so we are required to create a new named connection.

Post by Esteban Pacheco
Hello,
I had the same problem, I couldnt find a real solution to it. The only way
I was able to make it work on production was by adding the 2 dbx .ini files
that controlled the supported connections on the same directory as my
executable.
You can look for a previous post where I went through a big troubleshooting
without any positive results.
Let me know how it works for you.
Att.
Esteban Pacheco

Post by pete welch
When deploying an application that makes a stored procedure
call to SQL2K using dbEpress, an error pops up complaining
about one of the stored procedure parameters. However, if I run
the application from my development box, there are no
complaints and it works fine.
I add the file dbxmss30.dll to the deployed exe directory. I
didn't do anything like run regsvr32 on it. The DBX
documentation has few examples, so I have no idea what else
might be needed. Do I need to install some sort of SQL Server client in
addition to the dbxmss30.dll?
Another question is, is there a standard way to provide
authentication for a Windows-only Authentication mode in SQL2K
(assuming multiple pc-based clients that call a stored procedure on the
SQL Server)? My notion is to grant
Domain/Users access to the stored procedure since the SQL
server and the clients are all on the same domain. But, what do
I use for user and password in SQLConnection.Params? Maybe,
nothing -- leave them blank. There is another parameter in the
Params property of TSQLConnection called OS Authentication that
suggests a value of True or False. Can't find any documentation
on it but I guess it should be True.
I will be grateful for any ideas or related discussion.
Pete