Karen,

You are completely and absolutely WRONG!



Look at the codes again.


equals the path where the DBMAN files are located.

the . means + OR include.

then the following:


is the directory and file.

So, by taking your example:


Would be interpreted by the server as the following:


This is interpreted as total garbage to the web server.

Do you see what I mean? If not, go to perl.com and look for directory, path, ., etc. to find what I am talking about.

Regards,

------------------
Eliot Lee
Anthro TECH,L.L.C
www.anthrotech.com
----------------------

You're welcome Jim Day - as I indicated, this is not an area of expertise for me. One other thing I did notice however, on the perl scripts - I didn't see the line:

#!/usr/local/bin/perl at the top of the script. Could that be the cause of this grief?


------------------
~ ~ ~ ~ ~
Karen

Karen,

Nice try...But you do not need to have Perl paths in .cfg files and also required .pl files that work with .cgi scripts.

As you can see...In Jim's db.cgi script, he does have the Perl Path:


But good try....noneoftheless.



Regards,

------------------
Eliot Lee
Anthro TECH,L.L.C
www.anthrotech.com
----------------------

Hallelujah! I deleted the .htaccess file on my server and the login screen now appears. Looks like it was the server password protection which was preventing the authorization subroutine from working. Might want to add this one to the FAQ Eliot. Thanks for all of your help.

Great...Glad you got it to work.

Actually, you are more than welcome to add the .htaccess conflict in the FAQ. The FAQ is for ALL DBMAN users to add helpful tips and suggestions to other DBMAN users.

BTW: If you still want to use .htaccess, there is a Thread in the Discussion Forum that provides codes for using .htaccess.

Regards,

------------------
Eliot Lee
Anthro TECH,L.L.C
www.anthrotech.com
----------------------

Ok, I just added this to the FAQ resource directory. Hope the solution works for you as well Graffix.