×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Session.Browse syntax

Session.Browse syntax

Session.Browse syntax

(OP)
I want to find out how to use .browse.

How do I do a "not LIKE" in the filter syntax? != is for not EQUAL, but...

When .fetch is issued after a .browse (where only one record should be returned), does the engine still look through the entire table? For example, when doing a loop while .fetch, it seems to go into some sort of hang condition the second time the .fetch is done, and I can't get out of it (needs a reboot). Any ideas?

RE: Session.Browse syntax

The .Browse syntax is fairly simple. You just have to make sure that are quotes are recognized propertly. Either as quotes defining the entire string condition or as quotes around values in the string. The symbol that I would use for 'not equal to' is '<>'. I am not sure about a 'not Like' operator.

The browse is like a filter that is used by the .fetch. From what I understand the .fetch will stop at the first record that matches the filter. Then the next and the next, etc.. This means that it will look throuth the entire table when in a loop. (do while .fetch...). If you know that you will only get one result (search for ID field) then place the .fetch in an if-else statement and it will only go as far as it needs to because you stop it after it has found the record it is looking for. The second parameter in the browse (true, or false) is suppose to determine whether yu start at the begining or end of the table (go forwards or backwards). Thus if you know the records is recently added you can start from the end of the table and it might find the record faster. However you may end up with more problems in going backwards, it's also slightly slower than going forwards.

If you are having trouble with syntax post your code and we will have a look.

Thanks and Good Luck!

zemp

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close