after step 2,I have a error:
A fatal error has occured:

Can't use string ("1") as a HASH ref while "strict refs" in use at /home/cgi-bin/admin/GT/SQL/Table.pm line 76, line 1.

Please enable debugging in setup for more details


What I need to do?

This is the same error I am receiving while installiing v2.0.1. I've searched the forum for a fix and have not found anything useful. Can someone please identify what needs to be done to correct this problem? Thanks!

Are you updating an install from the betas? Did you run the alter table commands to add the extra fields? (if not, check the FAQ, I just added it).

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

Hello Pugdog, no I'm not upgrading from a beta. Upgrading from v1.2 however, there was nothing in v1.2 I needed to keep. The install program indicated this file was written during the installation ...

Unarchiving (644) /usr/local/etc/httpd/cgi-bin/links/admin/GT/SQL/Table.pm

There is nothing in the area of line 76 that I can identify as the source of the error:

# Some defaults for writting to
$self->{schema} ||= {};
$self->{schema}->{index} ||= {}; << Line 76
$self->{schema}->{unique} ||= {};
$self->{schema}->{cols} ||= {};
$self->{schema}->{pk} ||= [];
$self->{schema}->{fk} ||= {};


I was not able to locate anything in the FAQ's which relates to this problem.

Please - can anyone provid feedback on correcting this fatal error message?

A fatal error has occured:

Can't use string ("1") as a HASH ref while "strict refs" in use at /home/cgi-bin/admin/GT/SQL/Table.pm line 76, line 1.

This message was received after completing the set-up screen, Links SQL Setup - SQL Information.

Can you send me your log-on information and I'll take a look. I need to see what's going on. I have an idea of where the problem is, but I need to follow it from start to finish.

I'd need to re-install the program, so FTP/Telnet and your admin log on are needed. Don't post them, email them is better.

The error "1" like that, usually implies some "true" value is being used, rather than the expected hash value. It can mean the wrong parameters were input somewhere up the chain.


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