Alex,

In the 1.x versions, when adding in to the script, and using your own tables, or modified tables and routines, many of the loops in DBSQL.pm gave

[Mon Nov 27 20:18:06 2000] script.cgi: Use of uninitialized value in substitution iterator at admin/Links/Template.pm line 189

or similar warnings when iterating through the HASH of passed in values. I was able to hack around that in some cases by using if (defined ) constructs in DBSQL.pm, and at one point in my script I checked each input hash value, if if existed but not defined, set it to '' so that it didn't generate an error.

What I'm asking is, is this what you fixed up a short while ago in this code? So if a hash is passed in to the database routines, it doesn't "expect" to get a certain set of values, but handles "exceptions" as well?

Forms pass in a lot of "empty" tags, and the database routines need to be able to deal with it. I'm assuming the new methods do.

If this wasn't so new, I'd figure it out for myself <G> But it's easier to ask.



PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://postcards.com/FAQ