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

Calling another APP

  • Filter
  • Time
  • Show
Clear All
new posts

  • Calling another APP

    This may be a newbe question, but we have a very extensive application running in A5 ver 1.02. We have purchased ver 4, but are stymied on how to proceed. In ver 1.02, we didn't need to define all of the databases available to an application, but, it seems that they need to be defined in version 4. We thought that calling a separate application for each phase of our business would be the easiest solution. version 1 had an "app_run" command. We don't see it in version 4. How can we accomplish this.

    code is as follows:


    IF ACCESS=1011 .OR. ACCESS=839 .or. BETWEEN(ACCESS,15,20)

    END IF

    Our thoughts are to have the main application and form just perform the security check, then pass control off to the department-specific application.

    Any help would be appreciated.

    Tom Henkel

  • #2
    RE: Calling another APP

    Ver. 5 is supposed to have a "Load Database" command. You might be able to do it in ver. 4 using a sys_send_keys command - provided users have access to the controlpanel.
    AlphaBase Solutions, LLC


    • #3
      RE: Calling another APP

      How often do you want users to have access to the control panel? This is a massive collection of applications and databases, something along the lines of 15-20 separate functions(applications) and between 500 and 1000 tables and sets. This cannot be left up to a user to navigate through teh control panel. We have over 250 users, some on remote connections through a CITRIX server. We need an interface as simple as version 1.


      • #4
        RE: Calling another APP

        Check out the message threads:

        Question for Selwyn, 6/2/2000

        Switch database from form, 7/25/99

        The consensus online is that there is no way to use one app to run another. Instead, the paradigm is to develop a single 'database', then use a main menu form to branch to different modules in the application.

        -- tom


        • #5
          RE: Calling another APP

          It just seems so rediculous that something which worked so well under release 1 was abandoned with these newer versions.


          • #6
            RE: Calling another APP

            I agree. But the good news is that ver. 5 will have that command reinstated.
            AlphaBase Solutions, LLC



            • #7
              RE: Calling another APP


              My first impression from reading your initial message was that you are defining a separate database for each DBF file. I hope this is not the case because it is not necessary! The definition of "database" was changed between version 1 and version 4. (I think it was first changed in version 2 but I'm not sure.) In V1, a database equalled a DBF file. In V4, a database is a collection of DBF files.

              Having said that, I have had some luck with a simple sys_shell command to open another V4 database:
              sys_shell( "d:a5v4alpha5.exe G:A5v4ptrackerptracker.adb" )

              HOWEVER, I later abandoned it as unnecessary and even confusing. If applicable, I just put all the necessary tables and sets in one database. Where that doesn't make sense, I just let the user open another application.


              • #8
                RE: Calling another APP

                Oops! I forgot to fix the command to allow for the HTML. Here is the corrected command:

                sys_shell( "d:\a5v4\alpha5.exe G:\A5v4\ptracker\ptracker.adb" )

                Or, more generically:
                sys_shell( "A5 program> "Application file> )


                • #9
                  RE: Calling another APP

                  I think that the best way for anyone to invision what we do is to let you see our main app. Please remember that this is ver 1.02. Once you see what is going on, you might understand my frustration. We are a county government agency. We have applications that handle client information as well as employee information. I can't see how we could create an application that could hold all of our tables and sets. Our main signon screen captures user information and passes it throughout the system with the user. we need to keep this information flowing throughout all of our applications. see attached


                  • #10
                    RE: Calling another APP

                    Tom, adapting an existing system to a new way of doing things is never easy, and can certainly be frustrating... especially if the existing system works fine. This is often expressed by folks migrating their apps from Alpha Four to Alpha Five, for example.

                    In your case, you main menu apparently permits the user to 'call' a variety of applications, and then return to the main menu when each ends.

                    This is how my own system works in Alpha Five, but I don't call other applications, I call other forms, which call forms... and so on. At startup I, too, collect information that is stored in a series of global variables, which are available to any of the forms and scripts in the system.

                    If you want to convert your system using Alpha Five vers 4, I'd recommend you begin with a dummy table to which you can attach a main menu form. Convert one 'application' at a time, adding them all to the same folder and database. Start with the smallest ones to give yourself a bit of a break on the learning curve.

                    Good luck.

                    -- tom


                    • #11
                      RE: Calling another APP

                      My concern with adding everything into one enormous main application is one of maintenance. If the forms and reports tabs would cascade off of the table and set tab, then it wouldn't be such an overbearing task. In many instances, we have forms for different sets with the same name. How would one distinguish which one they are working with? I am wholeheartedly for upgrading to a more powerful Alpha5, but maintenance, at this point, would be a complete nightmare. We have over 250 users tied into this system daily. What sort of network and workstation problems are we going to encounter when loading such an app?