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

Vary data paths by installation

  • Filter
  • Time
  • Show
Clear All
new posts

    Vary data paths by installation

    I just ran into a problem I need some help with. I created a small application which has its own database tables and also accesses database tables from another, non-Alpha existing application. Here's the setup...

    Other application database tables folder - C:\LP
    My application and database tables folder - C:\LP\Dashboard

    Everything works fine when I install and run my application on my machine. However, I when I went to the customer's site, he had a slightly different setup, specifically...

    Other application database tables folder - C:\Data\LP
    My application and database tables folder - C:\Data\LP\Dashboard

    Since my application was looking for the other application's tables in C:\LP, it crashed saying it couldn't find the tables it was looking for. What can I do to make the other application's tables variable or installation specific? (Please keep in mind that some of the other application's tables are assigned to sets and reports.) Is there a way to tell Alpha5 to look for specific tables one level up from where the Alpha5 application is installed?

    Any help or suggestions would be appreciated. Thanks.

    Re: Vary data paths by installation

    Aliases (This is a link)
    There can be only one.


      Re: Vary data paths by installation

      Thanks for the quick reply. I see how I could use aliases when referring to a table in an Xbasic script or function, but how do I use the them to replace the Full Name that appears on the Table/Set tab of the Control Panel when I'm adding a table to the database? Thanks.


        Re: Vary data paths by installation

        You shouldn't need to do anything.

        Attached are screenshots of the "standard" AlphaSports installation and a copy of AlphaSports (windows explorer copy whole directory and pasted elsewhere).

        Alpha builds the paths relative to the location of the .adb file.

        Since my application was looking for the other application's tables in C:\LP
        I assumed you meant operations, etc.

        How did you create the installation file for the client installation?
        There can be only one.


          Re: Vary data paths by installation

          I guess I meant tables, operations, etc. The other application uses .dbf tables as well. It just puts them in a totally different location depending on who installed it in the 1st place.

          To create the client installation, I first used Alpha's installation creator. Unfortunately, when testing I ran into a problem, so then I just copied the files to their respective folders. That's when I ran into this problem. How would the Alpha5 installer know the location of the other application's database tables? (It's one folder level up from my Alpha application.) And if you use another installer (I'm very proficient in Wise), how would that know? I'm confused :(.


            Re: Vary data paths by installation

            When you open a data base you open the .adb. That's why the shortcut points to the .adb.

            The Alpha executable looks at the location of the .adb and "adjusts" if necessary the stored locations of the tables referenced in the .adb relative to the path to the .adb.

            Experiment a bit. Create a new database in some directory. Create one table in the database directory and then another table but save it in another directory. Exit Alpha.

            In explorer copy the new database directory to yet some other location. Open Alpha, navigate the the new new database directory and open the database. The database copy control panel will show the local table in the new new database directory but will show the external table in its created location.

            Harder to describe than it is to understand when you perform the above.
            There can be only one.


              Re: Vary data paths by installation

              I suppose since your client installations will have their own paths to the external tables you will have to create that directory structure on a machine of yours, populate the external directory with tables your application needs to reference, and build the installation on that application.

              In other words, since "up one level" has it's own path, you'll have to create it in your application before the install is built.

              I understand that you have limited control of where the other application stores its tables but if you make that one level down rather than one level up, the problem would be solved for you.

              Also if the path to the other application files was fixed and not relative to the Alpha database you would have no problem.
              Last edited by Stan Mathews; 02-03-2011, 01:10 PM.
              There can be only one.