Tom,
The first thing I would try is to rename your default.a4d to
default.a4d.bak, then create a simple default.a4d file and see if
Active4D will serve it.
It could simply contain:
<p>Some static Output</p>
<%
write("<p>Some interpreted Output</p>");
%>
If you get a 404 error (file not found) then I'd suspect your folder set
up on Windows isn't right. If this file serves both lines, then
something else isn't right.
You might want to put a TRACE in the 4D web server handler. You didn't
say if you were using 4D's web server or ITK, but I'd determine if the
web server is invoked before going deeper.
It might also be helpful to put some debug output at the top of your
regular default.a4d and dump the form variables collection. This will
let you see what the form variables are. Refer to the docs on how to do
this.
Also, if possible, it might help if you can post some code.
best,
Brad Perkins
Tom Lundeen wrote:
This is our first post to this list, so please be gentle! 8-)
We've successfully created a web site of sorts with Active 4D, and are
developing it for a specific client. Since we have the proof of concept
operational, we decided it was time to move it from our development Mac
server to a Win2K server, since that is what the client is using.
The database (4D 2003.7) functions just fine -- we typically develop on the
Mac and then move it to Windows for testing before installing updates on the
client. That's been no problem. However, we have not been able to get Active
4D to cooperate, and we're at a loss to understand why. We copied all of the
files, complete with directory structure, to the Windows box.
On our "default.a4d" page, we first test for the existence of form variables
to see if the user has already logged in. If so, we redirect the flow to
other pages; if not, we present our own log in page in the rest of the .a4d
document. When we log in to the account, our full page is correctly
presented -- but that's where it ends (including our understanding).
We had begun developing these pages some months ago, but then put it on the
back burner until a pressing update was installed about a month ago. Now, as
we're getting back to these pages, we're finding that we must have forgotten
something -- or Active 4D operates differently on Mac and Windows. We
present two form variables on the default.a4d page -- user name and
password. It's our understanding that the flow of control is then passed to
the "default.a4p" file, which calls our 4D method to validate the login.
Unfortunately, it never calls the method (which has a TRACE in the first
line).
We've gone back to the version on the Mac, and it still works properly. Even
though we have exactly the same configuration on the Windows side, all we
get is a 404 error. We don't have a clue what file is being requested
because we don't know what happens to the flow of control. We've searched
every A4D document we have, and the characters "a4p" do not appear ANYWHERE.
Maybe we've missed something else, but in any case, we're absolutely dead in
the water. And we are one version behind on A4D -- the new version came out
just after we had started with it, and we didn't want to spend TOO much time
dealing with the changes. Once we're fairly well up to speed, it's almost
certain that it will happen.
Thanks in advance for any help you might be able to provide!
Tom Lundeen
TLC - Tom Lundeen Consulting
Prairie Solutions, Inc.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
