I know I'm missing some simple thing that's probably right in front of my nose, but I'm stumped and hope someone might be able to help me. Here's the situation:
I'm working on a project long distance. I'm using VB6.0 and SQL Server 2000.
I work local and then upload and install stuff remotely. My local
machine has SQL server on it while the remote machine connects to SQL
Server on a dedicated machine (my VB
interface resides on the remote
machine and connects to the dedicated server using ADODB, etc.) All
connections work remotely, that's not the problem. The problem is in a stored proc that works on my local machine and doesn't on the client's.
The proc very simply calculates out the cost of a truckload of timber
and updates the cost field in the loads table with that calculated
cost. The procedure works perfectly on my local machine, but when it
is run on the client's machine, it places NULL in the cost field of
each load. I have run the proc in debug mode on both my machine and
the client's and it works on my machine, but on the client's, I pass in the three parameters and then click on execute and it doesn't even appear to run. I'm at a loss. I thought it might be a rights issue so I temporarily set the program to SA and it still didn't work. I even tried debugging as SA and it still doesn't work.
I checked the properties of the proc and it showed public with execute unchecked so I checked it and it still didn't work. I'm lost.
Any ideas as to where I might look for a solution or should I just
shoot the client (just kidding :-)