Ok, watch out since this is going to be a little long winded. I'm assuming that you have a unix system to which you have telnet access and also a little bit of unix and perl experience.
First off, there's a few things to be aware of. The administration panels for Links SQL are quite flexible, if you look in your cgi/admin/defs directory, you'll see lots of different .def files. All .def files, with the exception of database.def correspond to a database table that Links SQL uses. As well, if you're using a "prefix" for each of your tables (so you don't have table name collisions with other applications) you'll also see that all the .def files will be prefixed with that value.
For the database administration screens you won't need to do too much work. Try this, you probably already have a database table called "ClickTrack". Try the following URL (reformatted so that it functions with your system)
Code:
http://www.yourhost.com/.... admin/admin.cgi?do=editor_table_form&db=ClickTrack
You can do that with any of the other tables that you find in the defs directory. Just remember to remove the prefix from the tablename when you're passing it to the admin.cgi. As an example, if the prefix was lsql_, the def file may be named lsql_ClickTrack.def but you must do ...form&db=ClickTrack. Not ...form&db=lsql_ClickTrack
If you want to create an additional table, using your favorite table creator make a new table as you'd like. There is only one restriction, if you are using prefixes, you
must use that prefix as part of your new tablename. Add the appropriate indexes, but dont add things like fulltext indexes quite yet, that's probably better handled by Links SQL.
Once the table is in the database, its format must be converted into a .def file so Links SQL will recognise it. I've uploaded a script, defops.cgi that will do that job for you. Before you upload it to your server however, make sure you change the paths in the script to reflect your installation. It won't work otherwise. I'd recommend uploading it to your admin directory so it's password protected. So to pull the data: if you have a prefix of "lsql_" the table you wanted to pull would be named something like "lsql_Notes". With that tablename, call defops.cgi by doing:
This is a script I use for myself so the error reporting is sorely lacking

But if you see no message, the process was probably successful. Check in the .def path to make sure.
Finally, in your admin templates, look for a file called db_nav.html and add your tablename to the option list like the following:
Code:
<option>Category</option>
<option>Links</option>
<option>Users</option>
<option>Notes</option>
<option>Reviews</option>
It should now be available in your admin panel.
A couple of tricks for the road.
If you're going to create the table, try naming the primary key "ID", it will make the quick search function properly on your system.
For indexing, go to the properties and change the indexing there. It will probably show "nonindexed" initially but set your weights on columns and searching will be functional from then on. (you'll have to write some custom code to take advantage of this, however, which is beyond the scope of this post)
Not a trick, but the next time you make a backup, Links SQL will backup this new table as well.
Finally, a really cool trick is a global like the following. This assumes we're using the previous example of lsql_Notes and that is has a primary key named "ID" .
Code:
sub {
my $id = shift;
my $tbl = $DB->table('Notes');
my $rec = $tbl->get( $id ) or return;
my $tags; @$tags{ map { "Notes_" } keys %$rec} = values %$rec;
}
This will allow you to pull the record information for a particular record into any of your templates as long as you know what the ID for that record is. In this case, once the call has been made, all the columns of Notes will be available as a tag, just that you'll have to prefix the column name with "Notes_".
Hope this helps. This is not an "official" feature so things may change in the future or suddenly stop working. You may want to look into using a plugin instead at some point.