I have a small ASP.NET app that calls VFP Stored Procedure. It works without a problem for some customers. But one customer has a problem where SP returns error: "Invalid Path of File Name." I am trying to figure out what in the Stored Procedure causes this error message.
I have a suspicion that maybe when the code in the stored procedure opens a table (command USE MyTable), I don't specify where the table is. My understanding was that if the code reached the Stored Procedure, it knows that the tables are in the same folder as the database. And, as I said, it works for other customers. Could it be that something in the environment of this customer is such that the stored procedure can't find the table? Would it return error "Invalid Path of File Name" in this case?.
If you can think of where else this type of error message can be initiated, please let me know.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
