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

Announcement

Collapse

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

Issue with XML Parse/Arguments Build 6232-5386

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Davidk
    replied
    Re: Issue with XML Parse/Arguments Build 6232-5386

    That's why you should just parse it into a pointer variable and use that... it's safer than depending on some weird Alpha stuff that's going on. And... you need to test the data you're assigning.

    Leave a comment:


  • ssmoore1
    replied
    Re: Issue with XML Parse/Arguments Build 6232-5386

    Hey David,

    Thanks for jumping in, much appreciated.

    Basically I just wanted to get the value from the SQL Query (i.e invoice # 231) and then pass it into the variable. From there I was going to use that variable to add it to an argument for my own SQL query.

    Strangely I found this works:

    del_args.set("InvoiceID",Myarguments[1].data)

    but this doesn't

    temp_inv_header = MyArguments[1].data



    So it finds the argument value in the XML when I pass it directly into my own arguments, but when I want to pass it to a variable can't find it.

    I will also look at your other options thanks!

    Scott

    Leave a comment:


  • Davidk
    replied
    Re: Issue with XML Parse/Arguments Build 6232-5386

    The assumption is you're using a grid.

    I'm unsure why Alpha is showing array values for a variable that is not an array... however... it is.
    e.argsxml is not an array... it is a property variable.

    Here's the weird-er thing... it's not failing for me.

    But... depending on what you're doing in the grid... update, delete, insert... you are looking at a possible failure. MyArguments[1].data may not be a number... it could be a character... but you're assigning it to temp_inv_header... which is dimmed as a number.

    Overall, it's unclear what you want to do... but... you're better off converting the e.argsxml into a property variable... and then getting what you want from there.

    Code:
    dim myArgs as p
    *property_from_xml(e.argsxml,myArgs)

    Leave a comment:


  • ssmoore1
    started a topic Issue with XML Parse/Arguments Build 6232-5386

    Issue with XML Parse/Arguments Build 6232-5386

    Hi,

    In the latest release there seems to be an issue with reading the XML in onBeforeSQLCommandExecute server-side event (6232-5386).

    My current code does this:

    dim MyArguments as SQL::Arguments
    MyArguments.xml = e.argsxml

    delete temp_inv_header

    dim temp_inv_header as n

    temp_inv_header = MyArguments[1].data

    But I get an error that it can't find the value in MyArguments[1].data. However, in the debugger in the variable screen at the bottom entering that value does return a result.

    Is there a new way to code this or could it be a bug?

    Thanks,

    Scott
Working...
X