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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Out of windows memory

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Out of windows memory

    Hi,
    I was adding to a xbasic script, which is not that long, and then got a message "out of windows memory".
    Any help to resolve this would be appreciated.

    Brian
    Tags: None
    #2
    RE: Out of windows memory

    Brian,

    You'll find a number of threads on this, using the Search feature of the message board.

    If you're working on an inline xbasic action scripting command, the error message means that your script is too long. Convert your action script to Xbasic Code, or use more than one inline xbasic action scripting commands.

    The inline xbasic editor was apparently designed for short scripts. This is a limitation in Action Scripting, only. if you use the regular code editor you can write much longer scripts... however, if you keep going you will eventually hit a limit there, too. If that happens you need to organize things differently, perhaps using saved custom user-defined functions which you call, or by putting parts of the larger script in smaller saved global scripts that you 'play'.

    -- tom

    Comment

      #3
      RE: Out of windows memory

      Hi Tom,

      Thanks for the help. Tried searching, but couldn't see anything really related to this situation.
      It was a script on a button, from action scripting using the xbasic command. I was writing it in xbasic.
      In A4 each script had a name, and could be played from another script. There was also a script library.
      I've gone thru the book, but don't see how name a script and then play in from another, as per A4. It would be really useful to me.
      I'll have to experiment with the code editor, I guess.

      As long as it is normal it is ok; I had visions of having reached the limit of our computor, before even finishing the app let alone entering data. You have eased my fears.

      Thanks


      Brian

      Comment

        #4
        RE: Out of windows memory

        Brian

        You are learning one of the basic lessons about the transition for A4 to A5. Nearly everything is different. Database principles haven't changed, but the implementation in a Windows environment is very different from a DOS environment. The hardest part for me was to completely forget how I did it in A4 and start learning the new terminology and methods of A5. I soon learned to read the manuals completely before I tried anything and then build slowly. The learning curve is steep, but the rewards are large.

        In A5, scripts can be created in the code editor. These scripts, functions, menus, etc are saved in the database data dictionary. A database in A5 is similar to an application in A4, it contains the tables with the data, forms, etc. In a sense the script library in A4 is replaced by scripts saved in the database data dictionary.

        If a script is created in the code editor, you can run the script from anywhere with script_play(). The only concern is the context of the code. Some script code will only work if it is run from a form because of field references, etc. A script created from within a form can only be run by the object it is attached to. For instance, if you have code attached to a button, it can only be accessed directly from the button.

        There are a couple basic options if you want to use this same code elsewhere. First, you could create a standalone script in the code editor and use script_play() everywhere you want to run the code. You can create a user defined function with the code and then call the function. You can just copy the code, if it is in xbasic, and paste it in another xbasic script. If the code is on a button, you can address the button object and "push" the button with xbasic. A5 in all versions is very flexible, but sometimes the variety of options can be confusing. I use all of the above options, depending on the situation.

        As Tom points, out inline xbasic is very limited. If it is converted to regular xbasic, there are fewer limitations. However, action scripting is a good learning tool to give an idea of proper syntax. In A5V4, an xbasic script can be over 2000 lines long. I did an experiment some time ago and didn't hit any limits until well after 2000 lines. You can build some very complex code in that many lines.

        Jerry

        Comment

          #5
          RE: Out of windows memory

          Jerry,
          Thanks for the info and advice.
          If I use the code editor to creat a script, do I name it in order to distinguish different scripts.

          Thanks again,

          Brian.

          Comment

            #6
            RE: Out of windows memory

            Brian

            The code editor will require a unique name for every script. Every developer seems to have their own ideas about naming scripts, etc. The best advice is to use short, descriptive names. If I create a script that is used by a specific form, I use abbreviations to indicate the form and the action. For instance, if the code is for the OnSave event on an inventory form, I might name the script "frm_Inv_OnSave". In the form OnSave event, the only code would be

            script_play("frm_Inv_OnSave").

            I may have a script to reindex some tables. It might be simply called "Reindex_tables". The name is arbitrary, although there are some reserved names. Avoid names that are the same as existing A5 functions or actions. Don't use spaces and unusual punctuation. Normally, the only non alpha numeric character that should be used is the underline. There is a name length limit, which I think is 22 characters. It is common practice to use a naming convention that groups common elements. For instance, I start all menus with "M_", all toolbars with "T_", and all scripts attached to a form with "Frm_" or "F_". The name should be descriptive enough that you know what it is. Any script attached directly to an object on a form is not named explicitely, since it only exists as an action attached to the object.

            Jerry

            Comment

              #7
              RE: Out of windows memory

              Jerry,
              Thanks, I'll play with the idea and see how it works out for me.
              Your info and advice is greatly appreciated. I'll let you know how it all works out. I started doing anything at all in computors with A4 ver 2 a lot of years ago, so moving to A5 is a complete change. The more I find out, the more I realise I need to read more.
              Thanks,

              Brian.

              Comment

                #8
                RE: Out of windows memory

                Brian

                I started with Alpha with a4v2. I made the transition to Windows based databases with A5v1 and it was a steep learning curve. I found the best method to learn the program was to read a section of the manual and then slowly apply the new information. Like most users, I am still learning, but I am glad I started when I did instead of sticking with DOS too long. DOS may not be dead, but it certainly is in retirement.

                Jerry

                Comment

                Previous template Next
                Working...
                X