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

Need help interacting with XBasic back end

  • Filter
  • Time
  • Show
Clear All
new posts

    Need help interacting with XBasic back end

    Hello person smarter than me,

    In a previous post (edit: now post #1 of this thread) I asked for help interacting with an object-oriented back end that I had implemented in XBasic. I'm new to Alpha Anywhere, so I may have done things in conflict with the Alpha way. Anyhow, I have re-implemented the back end now so that my interface is via multiple functions that interact with the appropriate objects. Everything that needs to persist and thus be available to every object and function is maintained as a global variable (yeah, I know). This includes an SQL::Arguments object and collections containing SQL statements and corresponding JSON array results. The "controller" functions correspond to user actions, so I have such XBasic functions as GetDeliveries() which returns a JSON array of deliveries retrieved from a MySQL database. I take care of connections in the back end via a config file. GetDeliveries depends, for example, upon results obtained by GetRoute on a prior action. Other subsequent actions depend upon the results from GetDeliveries, again which are stored in a collection of results. I intend for the GetDeliveries results to be displayed in a list control called Deliveries on the Deliveries UX web component. The user will then select a delivery item which will trigger calling of GetDelivery(ItemNo). ItemNo must be passed into GetDelivery which will return the delivery item from the list obtained by GetDeliveries for display on the Delivery UX component. The entire app is intended to be built around this concept. In general, XBasic functions that build lists have no arguments, and those that retrieve an item from the list have one, ItemNo. The list queries depend upon the SQL::Arguments that have been set along the way and maintained globally. I can run the entire back end via a UnitTest script that calls LoginUser, then GetDeliveries, then GetDelivery, etc. in a heirarchy. Now I want to hook up the working back end to a front end with UX components Login, Deliveries, Delivery, etc. I also have table update functions that accept the values to be updated, like UpdateDelivery(par1 As C, par2 As C, par3 As C).

    My question here is, "How do I now hook up this back end to a front end comprised of 11 or so UX components (app screens)?" Is it even viable under Alpha Anywhere as I have presumed? Once I get things working on this small app, I hope to employ the same substructure for a much larger app full of very complex queries.

    I assume that I need Ajax callbacks for the retrieval of selected items, and the callbacks should return Javascript to display the subordinate UX component along with the data that will populate it. Am I on the right track here? Can someone provide a simple example or explanation of the right way to implement this? I have prototypes of my front end with navigation in place. I have tested the back end. I just don't know how properly to link the two up. I'm willing to change paradigms if needed.

    Thanks in advance for your help.
    Last edited by Al Buchholz; 04-18-2014, 11:31 AM. Reason: merge threads