Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

xbasic replacement of lookupc() statement for SQL backend

  • Filter
  • Time
  • Show
Clear All
new posts

  • xbasic replacement of lookupc() statement for SQL backend

    For the past several months, I have been converting my existing v9 web application to use SQL as the backend with v10 on the front end. I am nearing completion with the finer details remaining. For the most part I have not encountered too many problems and loving the overall results.

    However I do have a several a5w pages with xbasic code running some background activities using lookupc() functions at various points.

    I am not clear on how best to replace the lookupc() in xbasic to access SQL tables to lookup an indexed value which can then be inserted into a variable for the rest of the existing xbasic code to run.

    I am sure there is no direct replacement that I could simply "drop into" my lookupc() statements. So my question is how best to deal with this?

    I have quite a few such statements throughout several different a5w pages. I know that active linked tables won't work either because they donít support indexes used in the lookup() statement (and I prefer to not use active linked tables anyway, if possible).

    I know that there are quite a few others looking to make this leap and hopefully the answer here will help them as well.

    Any thoughts? Thanks!

    ps: Be sure to check out the new v10 action javascript "lookup and fill-in", which is wonderful for looking up sql or dbf tables with a grid!

  • #2
    Re: xbasic replacement of lookupc() statement for SQL backend

    I thought I best give an example to be more specific:

    Here is one example of a lookupc() being used after the log on page to capture a session variable based on the user:

    HTML Code:
    session.__protected__clientid = lookupc("F",session.__protected__ulink,"client_id","C:\USMON\child_web_user","Id")
    So if the "child_web_user" is now an SQL table, how would I capture the "client_id" to be used in the xbasic code?


    • #3
      Re: xbasic replacement of lookupc() statement for SQL backend

      What SQL does best is to select records, so a similar thing I do is

      if eval_valid("session.__protected__clid")=.f.
      dim GSVSelect as c
      dim gsv as SQL::connection
      dim grs as SQL::ResultSet
      if"::name::egw") 'connect to database 
       GSVSelect="SELECT cl_id FROM employees WHERE ( em_id ="+session.__protected__ulink )
      if gsv.Execute(GSVSelect)
        dim session.__protected__clid as n"cl_id")
      end if
      end if
      end if
      There may also be an SQL::Lookup command, but I haven't found it.

      Pat Bremkamp
      MindKicks Consulting


      • #4
        Re: xbasic replacement of lookupc() statement for SQL backend


        Thank you.

        So much to replace for just one function!

        As it is with many things, Alpha has spoiled us with certain functions that just won't be as convenient to replace using SQL (and vise versa I am sure).

        I will use this - thanks again.


        • #5
          Re: xbasic replacement of lookupc() statement for SQL backend

          Lookup() function does work with active linked tables, dont know if lookupc() works too.


          • #6
            Re: xbasic replacement of lookupc() statement for SQL backend


            You are correct - lookup() did worked well when I created an active link. Because I have like 15 session variables to load upon login, I decided to go with your method due to the ease of coding (for a non-coder).

            However, I did heard somewhere that with the web and SQL we should avoid active link tables if possible as it is an extra process (nothing is free). So I am hoping that I don't take a noticeable performance hit - but then again it is just one small table so we will see.



            • #7
              Re: xbasic replacement of lookupc() statement for SQL backend

              Yes you'r right nothing is for free

              But by programing in xbasic you'r allready adding some extra steps because as far as I know xbasic gets converted to native c++ but as computing power gets better this "extra steps" are less noticeable

              it would be great if like Pat said an 'SQL::Lookup' function actualy existed