I hope one of you can help me debug this.  I think it's the last of the Pg problems.  (Posts/Boards/Categories are all working now)

At the bottom of sub Register3() in Register.pl the program is updating the lastmember value to the $newuserid

This is giving an error because this value is NULL.
Usually I'm pretty good about debugging and finding where the problem is, but I can't find where $newuserid gets assigned.  The only other place I've even seen it is in a link destination a few lines above.

Divolging into this a little more while typing this, I know the problem is somewhere between Register3() and Validate().  Actually that might be the answer somewhere in GetMemberID and SaveMemberID

Any help is appreciated

I was just joking... I still have the problem.  This is where I know it is:
     $sql->set('value');
     $sql->update($newuserid,'lastmember');

$newuserid is NULL.
Any help on where it gets populated is appreciated!!!!!

Argh I'm back to the SaveMemberID dilemma from Load.pl

OMG I finally found it.  As I assumed.

$newuserid = $savememberid->insert(@memvals);

So for anyone who really wants to know the issue was in the: the INSERT statement - which is the Pg.pm driver I modified from MySQL.pm

In it there used to "return($sth->{mysql_insertid});" which returns the id of the last record recorded.  This is one of the better qualities of MySQL, however PostgreSQL isn't as fortunate.

I had to custom make the query SELECT \"last_value\" FROM $schema\.$self->{_table}_id_seq;
Processed it would turn out to something like SELECT "last_value" FROM eblah.members_id_seq;

This worked perfectly in the past.  So what was the problem this time?
I'll tell you.  Every sequence set up in PostgreSQL had the structure <tbl name>_id_seq except one.  Guess which one didn't.  You got it, members_userid_seq was what it was called.  So the query couldn't find members_id_seq because it didn't exist.  Therefore no userid value was returned.

Solution, fix the table setup structure.