Hi There!

I've been playing around trying to get a handle on dbman, but I guess I'm missing something. Trying to follow the directions to create a new database, I copied all the default files and renamed them "archive" and then made what I understood to be the appropriate changes in the file now named "archive.cfg" but when I tried to open the new file using "http:\\(myURL)\cgi-bin\dbman?=archive" in the location address on Netscape Communicator, I get:

Error Message : Error loading required libraries.
Check that they exist, permissions are set correctly and that they compile.
Reason: Unrecognized character \377 at c:\web\(myURL)\cgi-bin\dbman/archive.cfg line 1.


I've checked and rechecked and compared the new "archive.cfg" to the "default.cfg" and do not see any difference. (BTW - the demo using the default files provided works fine!)
What am I missing or doing wrong? Anyone had the same experience or got any ideas?

------------------
BigBritchs
BigBritchs@IDunno4Recipes.com


[This message has been edited by BigBritchs (edited May 16, 1999).]

Try

"http:\\(myURL)\cgi-bin\dbman?db=archive"



------------------
JPD

Thanks for getting back to me so quickly!

In my original post I misstypes the URL address with \\ instead of //. Stupid newbie mistake! Anyway, I tried both of the following:

http://(myURL)/cgi-bin/dbman/db.cgi?db=archive

and got the same error message noted above.

So I tried:

http://(myURL)/cgi-bin/dbman/dbman?db=archive

and got a 404 error.

Then I tried:

http://(myURL)/cgi-bin/dbman/db.cgi?=archive

AND IT WORKED! Well, maybe I'll get the hang of this someday. Meanwhile, did you get my email? Hope so!

Thanks again,

------------------
BigBritchs
BigBritchs@IDunno4Recipes.com

Yep. I got it. I'll be back to you.

I don't why it would work without having the "db" part of the URL, but if it works, I guess that's all that matters.


------------------
JPD

Oops! I guess "http://mydomain/cgi-bin/dbman/db.cgi?=archive" didn't really work afterall!!! What I got was the demo default database NOT the new database called "archive" I had made by copying the default files and renaming them "archive."

I discovered that the proper way to edit the 1st line in the db.cgi file was NOT "http://mydomain/cgi-bin/dbman" but "c:/web/mydomain(no .com)/cgi-bin/dbman" so I made the same change in the 1st line of my new "archive.cfg" file hoping that would work. Unfortunately, I still got the folllowing error message:

CGI ERROR
==========================================
Error Message : Error loading required libraries.
Check that they exist, permissions are set correctly and that they compile.
Reason: Unrecognized character \377 at c:/web/idunno4recipes/cgi-bin/dbman/archive.cfg line 1.

Script Location : C:\web\mydomain\cgi-bin\dbman\db.cgi
Perl Version : 5.00502
Setup File : archive.cfg

Form Variables
-------------------------------------------
db : archive

What in heck am I doing wrong? I just don't get it!

PS to JPDeni - I got your email and am still considering it. I had to take a few days off from this project, but will get back to you if I can ever get these fundamentals down!

Thanks,

Big Britchs



------------------
BigBritchs
BigBritchs@IDunno4Recipes.com



[This message has been edited by BigBritchs (edited May 30, 1999).]

I see. Sorry 'bout that.

I certainly have never heard of character \377 and don't know what it means. But I do know that when an error message refers to a line number, it includes comment lines. Try taking out the very first line of your archive.cfg file. It's just a # on that line anyway (or maybe something else that's invisible is there too).


------------------
JPD

The line in your .cfg file must be a URL, while the line in your db.cgi file (if you need to add a line at all) is a path.

At this point, I'll need to see your .cfg file in order to be able to answer any more questions. Please copy it to a web-accessible directory (one where you would place an .html file) and rename it to archive_cfg.txt. Then tell me where I can see it.

------------------
JPD

Hi Again!

I have put a copy of the archive.cfg here:

http://www.IDunno4Recipes.com/dbman/archive_cfg.txt

Thanks again for any help you can provide. This is driving me nuts! I know it can't be as difficult as I am making it.


------------------
BigBritchs
BigBritchs@IDunno4Recipes.com

It seems to be working now. I logged on by going to each of the top three URLs in your .cfg file and it worked. (The Banana Drop Cookies sound good! )

Are you still having a problem? If so, what exactly causes the problem?


------------------
JPD

Hi Again!

Thanks for dropping by. The problem is with the archive.cgf not the default.cgf. The following works just fine:

http://www.IDunno4Recipes.com/cgi-bin/dbman/db.cgi

What doesn't work is:

http://www.IDunno4Recipes.com/cgi-bin/dbman/db.cgi?db=archive

I created a whole separate set of files all named "archive" with the appropriate (I think) extentions and made what I thought I understood to be the appropriate changes neccessary in the "archive.cgf" file.

When I try to open the archive.cgf, I get the error message posted 05-30-99 04:27 PM PST.

Which of the above did you use? If you use:

http://www.IDunno4Recipes.com/cgi-bin/dbman/db.cgi?=archive

as posted 05-16-99 04:01 PM PST (notice the absence of the "db" between the ? and =) it opens the default.cfg and the default.db which is why you see the recipes. The archive.db still has the original data from the demo as it has not been changed yet.

------------------
BigBritchs
BigBritchs@IDunno4Recipes.com

Thanks, JP, I'll give that a try!

I assumed (stupid to assume anything with this) that the "line 1" referred to the first line of code! Thanks for the help.

Will get back to you on the email matter.


------------------
BigBritchs
BigBritchs@IDunno4Recipes.com

Hi Again!

Well, I guess it is time to put an end to this nonsense! Thanks for all your input, but eliminating the first line in the offending CFG file failed, too.

Out of exasperation and frustration I finally decided to chuck the entire file, copy and rename the default.cfg to archive.cfg, then edit the new file to point to the approprite database and other files.

Lo and behold, for whatever reason, that worked. I guess there was just something about my first file that db.cgi didn't like.

As far as this issue goes, I guess you can mark it RESOLVED (or whatever). Sorry to have pestered you so much over so little.

Maybe it is a good lesson, though. If its broke don't try to fix it, scrap it and do it over!

------------------
BigBritchs
BigBritchs@IDunno4Recipes.com