But it looks like I'll need to subclass wwSession when switching to SQL system files? I added my custom fields to the SQL tables but they are not being updated ...

I should be able to write the subclass code and then just point to it by redefining WWC_SQLSESSION in the include file, right?

--stein

I don't think so. The field 'extensions' are simply maps of the field names of the SQL cursor using SCATTER/GATHER NAME, so if you add the fields to the database they should show up on the oData member. The Fox code does the query directly, the SQL code uses a stored proc but it too does a SELECT * for LocateSession.

Just make sure that if you have Fox and SQL tables that both tables include all the same fields.

+++ Rick ---

You're right that the oData member gets populated correctly, but the session object relies on hard coded field references in the Save method to actually update the tables.

IF llIsSession = 1 && Session Exists
	THIS.oSQL.Execute(;
	           "UPDATE wwSession SET " + ;
		             "SessionId=?loData.SessionId," + ;
		             "UserId=?loData.UserId," + ;
		             "FirstOn=?loData.FirstOn," + ;
		             "LastOn=?loData.LastOn," +;
		             "Vars=?loData.Vars,"+;
		             "Browser=?loData.Browser,"+;
		             "IP=?loData.IP,"+;
		             "Hits=?loData.Hits " + ;
	             " WHERE SessionId=?loData.SessionId AND LastOn > '" + TTOC(DATETIME() - THIS.nSessionTimeOut) + "'")
ELSE
   THIS.oSQL.Execute("INSERT INTO wwSession (" + ;
                     "SessionId,UserId,FirstOn,LastOn,Vars,Browser,IP,Hits) VALUES "+;
                     "(?loData.Sessionid,?loData.Userid,?loData.FirstOn,?loData.LastOn,"+;
                     "?loData.Vars,?loData.Browser,?loData.IP,?loData.Hits)")
ENDIF

--stein