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

Problem with AEX files

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

    Problem with AEX files

    I am having a strange problem with an AEX file. Here is what happens. I right click on the white space of the code tab and compile all my scripts to an AEX. I accept the defaults in creating it. This creates an AEX file that is the same name as my database that will load automatically at startup. Then I delete all the scripts from the code tab.

    Here is my problem. When I distribute my as an update (no .dbf, .cdx, or .fpt files) in an install file, when the database is run it causes an error on one of the scripts. If I go back and just restore the scripts to the code tab, all works fine. So it would seem that the AEX is fouled in some way. Any ideas what could be causing this and, more importantly, how to fix it?

    Howard
    Howard G. Cornett, Independent Consultant

    #2
    What's the error?
    -Steve
    sigpic

    Comment


      #3
      Howard, I seem to remember something like that happening when I first started uising AEX files. I'm not sure what it was, exactly. I sidestepped the issue of using the (then) database-named aex file and moved all the program code into a completely separate aex file. I left only menus and toolbars and some functions in the database library.

      Funny, I just tried putting all the remaining stuff back into the database aex and the app won't open. It looks like one of the encryption functions won't work. I don't have time to dig into it now, unfortunately.

      Finian
      Finian

      Comment


        #4
        Error Message

        The error message is:

        Script:Est_onEnter line:218
        invalid field handle

        Line 218 looks like this:

        choiceC = lookupn("C",PART_DETAIL->B203_PREP_SOURCE,"Camera_film_per_sq_area","prep record","Prep_Source")

        There is no problem with this line if the script is on the code tab, but when there is only the AEX I get the error.

        Howard
        Howard G. Cornett, Independent Consultant

        Comment


          #5
          Interesting, mine fails on a lookupc () which checks the password entered in the user table.

          Finian
          Finian

          Comment


            #6
            How are you initializing the .aex file? Is it being put in (a) the Addins_installed folder or (b) the application folder and then loaded with Load_library() or (c) the "database properties/compiled libraries"?

            I seem to recall similar problems in the past but I don't recall the details any more. I probably never truly understood the problem but only found a solution that worked through trial and error. If my memory is correct, I think the problem was when using Load_library() and it was mostly a problem the first time around. Reloading the app sometimes seemed to fix it?? I'm also thinking that an xbasic_wait_for_idle() might have been used.

            If I find where I used this, I'll let you know what I did. ---> Never mind, it was in my Trak-It SP program where I no longer use the aex file. I had too much trouble loading an aex file where items in the aex file were called in the autoexec script. However, unlike what it sounds like Howard is describing, I haven't experienced any issues that I can recall when loading an aex file and using it somewhere other than the autoexec. There have also been no problems when the aex file is in the Addins_installed folder.

            Comment


              #7
              It's in the ADB path

              The AEX file is in the ADB path and has the same name as the ADB. My understanding is that it should load automatically in this case. Am I wrong?

              Howard
              Howard G. Cornett, Independent Consultant

              Comment


                #8
                You are correct. As I said, it has been a long time since I experienced the issue and, now that you mention it, it's very possible that I had the issue with the aex named like the adb. I know that this was one of the things I tried - probably the first thing. I tried a number of methods to solve the problem - I just don't remember what all the problems or results were.

                Comment

                Working...
                X