B
Bob Whitehead
I have a client who has several machines on different platforms at the local workstation level. They're on a Windows 2000 network. I was asked to work on a project someone else had created. It's an Access DAta Project with a SQL Server backend.
When I use a Command object to run a stored procedure, which has parameters, I use code like this
CommandName.Parameters(1).Value = parameter valu
Whether there is only one parameter or more, I have encountered problems on a few of the machines that error on that line saying that the stored procedure requires a parameter and it was not supplied. Even though it was. On most of the machines, and on my development machine, it runs fine with no problems
I am wondering what on earth could be different about those machines. One is a Windows 98 machine, one is a Windows 2000 machine. Could it be the ADO version? When I got it, ADO version 2.1 was referenced. I haven't changed it. Could that be a problem? Has anyone experienced a problem like this?
Any and all help is greatly appreciated
You can respond here or e-mail me privately at [email protected]
THANKS!!!
Bo
When I use a Command object to run a stored procedure, which has parameters, I use code like this
CommandName.Parameters(1).Value = parameter valu
Whether there is only one parameter or more, I have encountered problems on a few of the machines that error on that line saying that the stored procedure requires a parameter and it was not supplied. Even though it was. On most of the machines, and on my development machine, it runs fine with no problems
I am wondering what on earth could be different about those machines. One is a Windows 98 machine, one is a Windows 2000 machine. Could it be the ADO version? When I got it, ADO version 2.1 was referenced. I haven't changed it. Could that be a problem? Has anyone experienced a problem like this?
Any and all help is greatly appreciated
You can respond here or e-mail me privately at [email protected]
THANKS!!!
Bo