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

VBA vs Xbasic question

  • Filter
  • Time
  • Show
Clear All
new posts

    VBA vs Xbasic question

    A customer of mine has an application written in Access & VBA. They've been down for the past two days (a fix was applied last night) because one of the variables in one of the forms had been created with an 'integer' value instead of a 'long integer' value. The integer value will only handle (approx) 32,000 records before it stops working and they hit the wall on Wednesday. And of course, as soon as the value was changed, the program starting working again.

    Here's my question. I've setup a lot of xBasic variables and I have never had to explicitly attach a variable to a form and I've never worried about table-record limits. Is this just dumb luck or have I never hit a record limit or am I missing something?

    My question has nothing to do with Alpha support. I'm just curious about the differences between VBA and Alpha/xBasic, if anyone has an opinion they'd like to share.


    Re: VBA vs xBasic question

    Check the helps for 'database specifications'.


    The help file topic "variable data types" indicates that numeric variables can hold up to 19 digits, presumably including the decimal and any decimal places.

    The help file topic "Creating a new table" shows the limits for table fields. Numeric table fields can be 19 wide, with up to 14 decimal places.

    All systems have limits.
    Last edited by Tom Cone Jr; 03-01-2013, 09:36 AM.


      Re: VBA vs xBasic question

      Tom - I am glad you found the solution. This is not an uncommon problem with VB style apps. I have run into this more than once where the original design was an integer and the customer exceeds the data type size limitations. Like you I found making the data type a Long resolves the problem.

      If they ever migrate to SQL Server, as sometimes becomes the case with Access apps, they will want make sure the data typing in SQL Server is done correctly. SQL Server now has Small Integer, Integer and Big Integer data types just to add to the confusion.

      John W.


        Re: VBA vs xBasic question

        That's certainly true about limits. No question. Still, it seemed odd that in VBA a variable would have to be defined in that manner. In Alpha, I don't remember ever having to worry about the total number of records associated with a particular variable and a particular form.

        This is really not a field we're talking about ---with field limitations--- but rather limitations associated with a variable.



          Re: VBA vs Xbasic question

          Tom B - Its not really odd in the VB world. They moved to strict data typing . Its a good thing actually, but once the variable is given a data type it remain that way until changed. As you know In VB or VBA the declaration might look something like this:

          Dim variableX as Integer - -- variableX will stay an integer until you change into a long---- Dim variableX as Long

          Most of us were trained that explicit data typing is the better coding practice. It helps with the code maintenance, being able to read the code, troubleshooting, ease of creating parameters for stored procs, avoiding datatype mismatch. In VB.Net I believe you cannot have untyped variables, its required. That mindset now filters back to through the whole VB eco-system.

          John W.


            Re: VBA vs Xbasic question


            Very different from we're all used to within A5. However, maybe Alpha is the "odd man out" in this situation.

            Thanks for your input. Very helpful.



              Re: VBA vs Xbasic question

              Originally posted by [email protected] View Post

              Very different from we're all used to within A5. However, maybe Alpha is the "odd man out" in this situation.

              Thanks for your input. Very helpful.

              Many, including Peter Wayne, long ago strongly recommended always using OPTION STRICT. If you aren't familiar with it, you should check it out in the help files.

              Raymond Lyons