I tried using my app with the hard coding on another workstation and got compilation errors. So I have removed the hard coded paths for my #include and @inserts, and will be putting them into each user's Start In folder (currently C:\Sesame for each client). Once I did that the program compiled nicely. The only #include file I am using is sbasic_include.sbas.
However, my lookups still fail in runtime. Hard-coded lookups work in sdesigner preview, however. That is, in Preview, this will work:
IF NOT @ISBLANK(DESCRIPTION_CODE)
THEN
{
DESC_LINE_1 = @XLU("F:\Sesame\Miara\Desccode.db", DESCRIPTION_CODE, "DESCCODE!KEY", "ENTRY_1")
If @Error then writeln("Lookup failed")
DESC_LINE_3 = @XLU("F:\Sesame\Miara\Desccode.db", DESCRIPTION_CODE, "DESCCODE!KEY", "ENTRY_2")
DESC_LINE_9 = @XLU("F:\Sesame\Miara\Desccode.db", DESCRIPTION_CODE, "DESCCODE!KEY", "ENTRY_3")
}
But this will not:
IF NOT @ISBLANK(DESCRIPTION_CODE)
THEN
{
DESC_LINE_1 = @XLU("Desccode.db", DESCRIPTION_CODE, "DESCCODE!KEY", "ENTRY_1")
If @Error then writeln("Lookup failed")
DESC_LINE_3 = @XLU("Desccode.db", DESCRIPTION_CODE, "DESCCODE!KEY", "ENTRY_2")
DESC_LINE_9 = @XLU("Desccode.db", DESCRIPTION_CODE, "DESCCODE!KEY", "ENTRY_3")
}
In spite of the fact that the app making this lookup and the target db both reside in F:\Sesame\Miara\, as seen by my workstation.
Neither of the above work in Runtime.
The only differences in the programs that I can see is that when I start up sdesigner from my workstation, my icon uses the command "C:\Sesame\Program\sdesigner.exe" and when I start Runtime it's "C:\Sesame\Program\sesame.exe -Client Miara-2000serve". Both have C:\Sesame as a Start In folder.
One other issue I haven't mentioned is that, since migrating my applications to the server, after I reconcile and then try to open my application, the process called "loading" goes very quickly, but then "saving" takes a very long time, upwards of 5 minutes, which is much longer than when it resided on my workstation. I'm not sure what to make of that.
Since I've been working with a .dsr that came along with the migration to the server, I decided to create a new .dsr using "redesign application" from runtime. The first two times I tried this it appeared that sdesigner hung, and clicking on the window gave me "this program is not responding". The third time I decided to wait it out. It took 10 minutes.
Anyhoo, once I got into the new .dsr, I checked to be sure that the programming was the same as when I was using the old one (it was) and I tried Preview. This time the hard-coded lookups did
not work, nor did (as before) the ones that should just reference the files in the working directory. So there's clearly a difference in the way sdesigner is seeing my network. Run from my C drive, sdesigner can see the lookup targets on F. Run from "redesign this application" it cannot. In any case, neither db's in hard coded paths nor db's that reside in the same directory as the app are working in Runtime.
Closing my app took 6 minutes. Saving my new .dsr took 4 minutes.
These things moved like lightning when the files were on my workstation. It's a Saturday and no one else is here, and mine is the only system attached to the server, so there's no network traffic that might be getting in the way. As you can imagine, this is all very frustrating, and I'm really at a loss to know what to do next.