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

file backup for client install

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

    file backup for client install

    Is it possible to backup and transfer to my client just one form? I've made a minor adjustment to a menu form and want to transfer only that form. No file names or extentions match it in the directory.
    Tags: None
    #2
    RE: file backup for client install

    Yes but you will need to send the proper files from the table that it's built on. If the form is built on a set, then you'll need to send the proper files for all tables in the set as well as the set files.

    As far as I know, you cannot pull out file extensions for just a form.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment

      #3
      RE: file backup for client install

      From reviewing the documentation for distributing a runtime application it lists the following extentions:
      ADB, ALB, ALM, ALX, CDX, DBF, DDD, DDM, DDX, FPT, SEM, SET, SEX. To update the application, without making any changes to the file structures, what files would have to be updated? Would it be all listed above with the exceptions of DBF, CDX, and FPT?

      Comment

        #4
        RE: file backup for client install

        Geoff - the simple answer to your last question is Yes.

        The answer to your first question requires a bit more explanation. You can easily send the latest layouts (forms, reports, browses, letters, labels) for a specific table or set but it becomes very difficult to send only one layout - not impossible but difficult. In most cases, sending all layouts for a specific table/set isn't much of an issue so I'll assume that's acceptable. One other minor issue just to be aware of - this will also send all the saved operations attached to that table or set.

        I also have a minor disagreement with Ken's comment. If all you do is add a layout to a set and none of the underlying tables are restructured, there is no need to send all the files for the underlying tables - just send the .sem, .set, and .sex files ("table_name>.se*).

        You can send separate files but I highly recommend sending files in groups based on the main file name. In other words, if you have a table called MyTable and want to send the updated layouts for that table, send all three files - MyTable.dd*.

        Comment

          #5
          RE: file backup for client install

          Geoff,

          See attached. Right under our noses. Guess noone's ever used this before, at least those of us who read your post.
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment

            #6
            RE: file backup for client install

            Ken,

            I believe that layout.send attaches a printed layout to an email.

            Bill
            Bill Hanigsberg

            Comment

              #7
              RE: file backup for client install

              Thanks Bill,

              Well.................I didn't research it. Oh well, wipe off the egg and try it again.

              kenn
              TYVM :) kenn

              Knowing what you can achieve will not become reality until you imagine and explore.

              Comment

              Previous template Next
              Working...
              X