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

how to use xbasic to perform CRUD operations

  • Filter
  • Time
  • Show
Clear All
new posts

  • how to use xbasic to perform CRUD operations

    Hi everyone!

    I have an UX component form which i want to use xbasic to perform insertion and deletion on a different tables. Below is the code i have written so far, and i have a button in the form which i use Javascript function on Ajax call back to carryout the operation.

    function ToSellStock as c (e as p)

    dim Quantity as n
    dim output as c =""
    dim conn as sql::Connection
    dim args as sql::arguments
    dim sqlInsert as c
    dim sqlInsert1 as c
    dim sqlUpdate as c
    dim rs as sql::ResultSet

    dim clientID as n=convert_type(e._currentRowDataNew.ClientID,"N")

    if e.datasubmitted.sellStockTypeId="" then
    output=output+"alert('"+"please select a stock to sell"+"');"

    else if e.datasubmitted.sellQuantity=""
    output=output+"alert('"+"please select quantity to be sold"+"');"

    else if e.datasubmitted.sellQuantity>e.datasubmitted.testQty
    output=output+"alert('"+"Stock quantity over range"+"');"

    else if e.datasubmitted.sellPrice=""
    output=output+"alert('"+"Stock price empty"+"');"

    else if e.datasubmitted.sellCommission=""
    output=output+"alert('"+"Commission field can not be empty"+"');"

    else if e.datasubmitted.sellRemark=""
    output=output+"alert('"+"Remark field is empty"+"');"

    else if e.datasubmitted.sellCreditId=""
    output=output+"alert('"+"Credit field is empty"+"');"


    dim sql as c="select Quantity from dbo.StockValuationSheets where ClientID="+e.datasubmitted.ClientID+" AND StockValuationSheetID="+e.datasubmitted.sellStockValuation+" AND StockTypeID="+e.datasubmitted.sellStockTypeId+""
    if .not. conn.Execute(sql)then
    end if

    Quantity =convert_type(rs.Data("Quantity"),"N")
    dim testQtyy as n=convert_type(e.datasubmitted.testQty,"N")
    if Quantity<=testQtyy then

    sqlInsert = "INSERT INTO dbo.ClientAccounts(ClientID,UserID,Credit,Reference,Description,StockValuationSheetID,CreditDefinitionID,SystemDate)VALUES("+e.datasubmitted.ClientID+", '"+e.datasubmitted.sellUserid+"',"+(e.datasubmitted.sellTotalCost+e.datasubmitted.sellCommission)+","+e.datasubmitted.sellReference+","+e.datasubmitted.sellDetails+",+"+e.datasubmitted.sellStockValuation+","+e.datasubmitted.sellCreditId+",'"+e.datasubmitted.sellDateBought+"')"
    sqlUpdate = "UPDATE dbo.StockValuationSheets SET Quantity=Quantity-"+e.datasubmitted.sellQuantity+",CreditDefinitionID="+e.datasubmitted.sellCreditId+",TotalCost="+e.datasubmitted.sellTotalCost+" where StockValuationSheetID="+e.datasubmitted.sellStockValuation+" AND ClientID ="+datasubmitted.ClientID+" "

    if .not. conn.Execute(sqlInsert)then

    output=output+"alert('"+"Client account have not been credited"+"');"
    if .not. conn.Execute(sqlUpdate)then

    output=output+"alert('"+"Error salling stock"+"');"
    output=output+"alert('"+"Stock sold to Client"+"');"

    end if

    end if
    end if

    end if
    end function

    I need someone to current me where i get it wrong.

    Thanks for your help in advance.

  • #2
    Re: how to use xbasic to perform CRUD operations

    First of all I would test for the empty values at the control level with validation (validation in the controls properties) so that the user cannot get this far without all of the fields properly filled.

    The only issue I see is that you don't need any database designation since you have created a connection to the database in the connection statements. I would get rid of all of the dbo. as in ,dbo.StockValuationSheets, dbo.ClientAccounts.

    I am not sure if anything is wrong with your if then else statements where you are inserting and updating.
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO.


    • #3
      Re: how to use xbasic to perform CRUD operations

      There are a few things you need to do.

      You should always test your open connection.
      Instead of using .not. to test your connection and sql calls, dim a flag as L and use that...

      dim flag as l
      flag = conn.Open("::name::Colink")
      if flag = .f. then
         'we have a problem
         'send back a message
      end if
      Then you can use the same flag throughout the rest of the calls that need testing.

      Next, use arguments in your SQL statements. Concatenating is a mess. You already dim it, but you don't use it.


      dim sql as c="SELECT Quantity from dbo.StockValuationSheets WHERE ClientID=:clientId AND StockValuationSheetID=:stockVal"

      dim sql as c
      sql = <<%str%
      SELECT Quantity from dbo.StockValuationSheets
      WHERE ClientID=:clientId AND StockValuationSheetID=:stockVal"
      Either way is much more readable.

      Finally, use the best friend you have in XBasic. Put a debug(1) statement at the top of your code... throughout your code... where ever... run your UX in LivePreview within Alpha and just step through your code. You'll soon see your errors.