NetTalk Central

Author Topic: Session Queue info not found? Error check on GSV?  (Read 2990 times)

JohanR

  • Sr. Member
  • ****
  • Posts: 366
    • View Profile
    • Email
Session Queue info not found? Error check on GSV?
« on: January 18, 2015, 09:48:18 PM »

Hi,

I have a small piece of code in the "processlink" embed to load the glo:dbowner variable.
This is to enable different users to connect to seperate DB's
The site is still quite simple with only a few pages, but on a specific page it seems as if the values in the session queue is blank, this then loads the master connection string again, and then everything falls over.
If I keep navigating the site it sorts itself out and finds the session queue values again on subsequent pages.

As if the session queue record retrieval failed in certain instances.


This has been working fine, but somewhere something has gone wrong.

I have added some debug code of my own to try and understand what is going wrong and was wondering if there is any error code check I can add to
confirm p_web.GSV() success or not?


   p_web._trace('session_ID  =' & p_web.sessionid)
   ! >>>>>> the login_status is set on the login screen, 1=valid, 0 or space = not logged in
   ! >>>>>> if logged in then I set the connection string to the string for that specific user
   ! >>>>>> else, I set the string to the master DB that is the default DB this also contains the master file with companies and users

   if p_web.GSV('login_status') = '1'
      glo:dbowner = p_web.GSV('dbowner')
   else
      glo:dbowner = 'Driver=PostgreSQL ODBC Driver(UNICODE); server=localhost; UID=demo; PWD=demo; database=wfmaster; PORT=5432;'
   end
   p_web._trace('yyy_session-DBOwner =' & p_web.GSV('dbowner') )
   p_web._trace(p_web.GSV('login_status') & ':DBOwner =' & glo:dbowner )

thanks in advance for any ideas

Johan



JohanR

  • Sr. Member
  • ****
  • Posts: 366
    • View Profile
    • Email
Re: Session Queue info not found? Error check on GSV?
« Reply #1 on: January 19, 2015, 07:45:22 AM »

Hi,

Some feedback.
Switching off multi tab support fixes the problem.
The problem also only happens on a specific page, so perhaps it's a combination of my coding and multi tab support that is causing a possible problem.

Will keep testing and checking to see where the issue is.

cheers,

Johan