I use an IF action which checks to see if <@VAR NAME=xxx SCOPE=USER> is
empty. I set this variable after a successful login.

If it is empty I do one of two things, either I have a branch to the login
page or I display a page with the login form.

When a taf needs both a sucessful login and a certain level of security I
check two things in the IF action. I check to see that the variable with the
security level is less than the level required OR I check to see if the
variable is empty. If either evaluates to be true then I display the "you're
not supposed to be here" type message.

With either of these scenarios I follow the IF action with an ELSE action
which contains the actual actions for the taf file.

Hope this helps,

Steve Smith

Skadt Information Solutions
Office: (519) 624-4388
GTA:    (416) 606-3885
Fax:    (519) 624-3353
Cell:   (416) 606-3885
Email:  [EMAIL PROTECTED]
Web:    http://www.skadt.com


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Campbell, Steve V.
Sent: July 16, 2002 3:10 PM
To: Multiple recipients of list witango-talk
Subject: RE: RE: RE: Re: Witango-Talk: Same Error Again -- follow up
security question


Thank you all for all these helpful insights. I do believe that as
Stefan said it's just the same error all over again.

One follow up question.

I am trying to remember what the standard security "If" statement is
that most use at the top of their tafs?  What I mean, is,  when you have
a large project with many tafs and the user tries to jump into a taf
without logging in thru your front door.  (or your login taf)

I thought once upon a time I used to see something along the lines of
<@ARG username> is not empty  (this is just one choice I thought I had
seen before)

The example above is of course, if the user is carrying that through
your site in their scope.

Hope this question makes sense

Steve

-----Original Message-----
From: Thomas Ferguson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 9:17 AM
To: Multiple recipients of list witango-talk
Subject: RE: RE: Re: Witango-Talk: Same Error Again

Also make sure you don't have any columns named with any word that
Access
might think was special.  I named a column "Type" once and got this
error.
When I changed the name of the column to "XX_Type" the problem went
away.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Stefan Gonick
Sent: Tuesday, July 16, 2002 9:47 AM
To: Multiple recipients of list witango-talk
Subject: RE: RE: Re: Witango-Talk: Same Error Again


Yes, that's the same error. Whenever the Access driver
complains about there being the wrong number of parameters,
it's because there is a mismatch between the fields in the action
and the database. I get this when I'm using a field in the action
that I later deleted from the table or renamed. Ignore the count
of how many it expected. That's a red herring.

Stefan

At 08:12 AM 7/16/2002 -0500, you wrote:
>Stefan
>I went thru and checked and yes, that's what it was. After those
>corrections I went back thru to run my taf and I ended up with this
>error.
>
>[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected
>25.
>07001
>
>
>Is this the same error?
>
>Steve
>
>-----Original Message-----
>From: Stefan Gonick [mailto:[EMAIL PROTECTED]]
>Sent: Monday, July 15, 2002 5:30 PM
>To: Multiple recipients of list witango-talk
>Subject: RE: Re: Witango-Talk: Same Error Again
>
>Hi Steve,
>
>That error is due to a mismatch of fields in the action
>and the database.
>
>Stefan
>
>At 05:16 PM 7/15/2002 -0500, you wrote:
> >I know I have posted about this error before. I know that I have seen
> >others post about it before. Once agani, I am stuck here tryign to
>debug
> >this thing.
> >
> >This is my error. Of course it's happening on the "insert" function.
> >
> >-3010 [Microsoft][ODBC Microsoft Access Driver]
> >         Too few parameters. Expected 3. 07001
> >
> >Any ideas would be appreciated.
> >Thanks
> >Steve
>
>_______________________________________________________________________
>_
> >TO UNSUBSCRIBE: send a plain text/US ASCII email to
>[EMAIL PROTECTED]
> >                 with unsubscribe witango-talk in the message body
>
>========================================================
>Database WebWorks: Dynamic web sites through database integration
>http://www.DatabaseWebWorks.com
>
>_______________________________________________________________________
_
>TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
>                 with unsubscribe witango-talk in the message body
>_______________________________________________________________________
_
>TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
>                 with unsubscribe witango-talk in the message body

========================================================
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to