The first problem we had was that Active4D's "Open Document" was not
finding/opening our files. It works fine when we access relative path names
(inside our web root) but not with absolute paths, so we suspect it is
something stupid we are doing with the "safe doc dirs" setting. The manual
indicates we need to start the path with a drive name. Based on my
understanding of examples in the manual, for testing purposes I tried
various settings such as the following, but to no avail...
safe doc dirs = /D safe doc dirs = D: safe doc dirs = D:/SomeFolder safe doc dirs = "D:/SomeFolder"
Well, you were right about needing to set "safe doc dirs" correctly, and the need to use absolute paths. The section called "Path Format" in the Configuration chapter (should be page 21) gives some examples of full Windows paths.
Of the ones you tried above, only the first is actually an absolute path. The others do not start with '/', so they are by definition web-root relative. The first one _should_ work, but it is not advisable to open an entire drive like that. You are better off setting it to the most specific directory you can, such as /D/SomeFolder.
Eventually we gave up and instead call a 4D method to find our file and
create our blob. We then let Active4D send the blob using "write blob". This
works fine except that we are now having a problem in that the file name
that the browser saves the file as is the same as our form processor page
(eg "GetDocument.a4p" instead of "SomeWordDoc.doc")
Please see the mailing list archive for a discussion of the solution to this:
http://www.mail-archive.com/[email protected]/ msg00701.html
Regards,
- Aparajita
_______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
