Thanks, I'll keep researching and let you know if I come up with anything. But same, if you find something, I would appreciate it. In another system I was involved in we did this with scripts but required the use of the ISQL.EXE command with parameters for the server, id, password, database, etc...
I was hoping to not have to invoke ISQL on each PC connected and just have the SQL engine handle it.... Maybe by inserting a record into the bogus table when the script was done pointing to the file name. Then with an INSERT TRIGGER to invoke the stored procedure to execute the .SQL script...
I know, not everything is easy...
>Hi Don ----
>
>Funny, I was just researching the script approach. I'm my Using SQL Server 6.5 book, they mention a \scripts subdirectory for .IDC scripts (maybe .SQL too?) so look at the SQLServer dir tree and maybe it's there?
>
>>I don't think so... But here is another approach we are now considering...
>>
>>Use VFP as the front end to create a .SQL script file with the desired statement, then have a single procedure on the back-end with one parameter... the name of the .SQL script. The stored procedure will do nothing but
>>
>>DO .SQL script (which is the entire query)
>>ERASE .SQL script
>>
>>This seams like an easier approach since VFP has all the low-level editing where we can create the file and assign the filename easier... How would I go about handling the file pathing and file name information as the parameter?
>>
>>
>>
>>
>>>Don, could you consider two-record interim table, i.e. you put actual values in two or more records there and then call stored procedure which will operate with these values, i.e. no macros substitution/variable needed.
>>>
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only