The path is very short and unremarkable. The shortcut points directly at rtime65w.exe. Rbase connects to the DB (another directory), CDs to the DIR containing the APX and calls the APX from there.
Tmp &Temp both refer to C:\windows\temp Temp must be writeable because there were 14 $$$ files (0 bytes) in the directory. Checking that made me wonder about the DIR holding the RBase exe's; there were no $$$ files there. I got the "Can't write temporary file" error only when Scratch wasn't set, but the app would at least start (if not run). After scratch was set the app wouldn't start, but all the commands in rbase.dat executed just fine. These folks actually have a decent in-house tech. He was just as mystified as myself... so I don't think there is a network issue. They have a Novel network, but this computer actually acts as a server for my apps on a peer-to-peer basis for occasional browsing by others. Another of my apps has run very well in this environment for more than a year (might be two+). For lack of a better answer, I'm wondering if a file might have been damaged while uploading it to their system, so I guess I'll look there next. Ben Petersen On 7 Feb 2003, at 21:56, Lawrence Lustig wrote: > > The next question would be, why would using "set scratch" keep > > the apx from running? > > Ben: > > Anything special about the path to your database? Is it very long, > does it contain spaces, or have long directory names? > > Also (this shouldn't matter) is the environment's TEMP setting > correct, and does it point to a real directory that is writeable? -- > Larry >
