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

alias for transfering a desktop application

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

    alias for transfering a desktop application

    Hi
    I have a desktop application with an import function. It takes an excel file called TMS_source_material and imports it into a table called tempsource.dbf. This works perfectly as planned. My problem arises when moving the application to a different machine. The import function can't find the specific file looking for it in e: when it is now in g: I've tried to figure out how to set up aliases for this to work going through settings etc but to no avail. Can anyone please help me understand what I need to do. I've set two Alias for the directory where the excel file is and the tempsource table namely:
    in the developing machine
    [source] e:\TMS\source
    [tempsource] e:\Tms\tempsource.dbf

    and in the secondary machine:
    [source] g:\TMS\source
    [tempsource] g:\Tms\tempsource.dbf

    I know I'm missing something. The online documentation I've poured over to no avail. What else do I need to do or do differently? Thanks for your time.

    DeanO

    #2
    Re: alias for tranfering a desktop application

    Dean,
    Are e and g mapped network drives? If so, your easiest method is to map the folders on the 2nd machine to drive 'e' and you would be good to go.

    If you don't want to use drive mapping, you could use the URL of the file "\\server\folder\filename" and then it wouldn't matter what the drive was mapped to.

    If the machines are running runtime, this might be the only solution.

    Otherwise, if you put the import onto the 2nd machine, you should be able to just change the drive letter in the import definition and, again you should be OK.

    You could, of course, convert the import to x-basic, an then write some code to determine the drive letter of the import file and dynamically substitute it into the code where appropriate.

    Tom

    Comment


      #3
      Re: alias for tranfering a desktop application

      Thanks Tom for your speedy reply.
      I took the second option mapping to the URL - I didn't realize I could do this. All works like clockwork, Have a great day and thanks again

      Comment


        #4
        Re: alias for tranfering a desktop application

        Originally posted by Tom Henkel View Post
        Dean,
        Are e and g mapped network drives? If so, your easiest method is to map the folders on the 2nd machine to drive 'e' and you would be good to go.

        If you don't want to use drive mapping, you could use the URL of the file "\\server\folder\filename" and then it wouldn't matter what the drive was mapped to.

        If the machines are running runtime, this might be the only solution.

        Otherwise, if you put the import onto the 2nd machine, you should be able to just change the drive letter in the import definition and, again you should be OK.

        You could, of course, convert the import to x-basic, an then write some code to determine the drive letter of the import file and dynamically substitute it into the code where appropriate.

        Tom

        Comment


          #5
          Re: alias for tranfering a desktop application

          not a problem. Glad it all worked out.

          Tom

          Comment


            #6
            Re: alias for tranfering a desktop application

            Can a wild card be used like \\Machine2\DataFile\*.dbf? I need to be able to access across a network an alpha database, then sometimes I want to take that same data on a usb drive and use the same data. I created several aliases but I am not having much luck in getting them access of the data files in those. I have 1 which is the drive letter assigned when the usb drive is attached to a machine and it needs to access the files across the network, and 1 where the usb drive would access data files on itself. I'm not quite understanding how the complete this process. I have forms on the usb drive which I do not want mingled with the forms on the network computer. I have managed to keep the forms on the usb drive only. Now I would like to access the network computer or the usb drive. Oh, I need to mention I have never figured out xbasic.

            Comment


              #7
              Re: alias for tranfering a desktop application

              Can a wild card be used like \\Machine2\DataFile\*.dbf?
              No.

              If you have a database where you have defined, say, an append from h:\data\test.dbf where H: is a network drive. If you are not connected to the network you can't run the append. If you plug in a usb drive which takes the drive letter M: and it has a folder data where there is a test.dbf, you can't run the append.

              As noted in another thread this morning, take a look at the tables/sets tab of the control panel and switch to detail view. Those ar the tables and sets and their locations you can use without using xbasic. It doesn't matter if there are dozens of dbf files in different folders with the same names you see, Alpha doesn't see them and can't use them.
              Last edited by Stan Mathews; 08-12-2015, 08:24 AM.
              There can be only one.

              Comment


                #8
                Re: alias for tranfering a desktop application

                So the idea of an alias works with only 1 file at a time or not necessarily for alpha database files???

                Comment


                  #9
                  Re: alias for tranfering a desktop application

                  An alias works for a database. It tells the database where to find the components of the database. It doesn't do anything at all if you don't use the alias in the definitions of your operations and code.
                  There can be only one.

                  Comment


                    #10
                    Re: alias for tranfering a desktop application

                    I have my old Alpha 4 manual. How much has xbasic changed since then??? If the only way I can do this is with code, maybe I can teach myself enough to be able to establish a universal location of the files.

                    Comment


                      #11
                      Re: alias for tranfering a desktop application

                      Linda,

                      Why not start a new thread and explain what you want to do? I'm thinking you want to have a database where, if you're using it on a machine with the usb drive plugged in, you have access to certain reports that are not available to other users.
                      There can be only one.

                      Comment

                      Working...
                      X