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

updating remote programs

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

    updating remote programs

    using pcanywhere
    if, locally, i delete *.dbf and *.fpt - and then upload *.* to the remote system - rebuild their indexes and compact their database - is there anything wrong with this approach - i tries it on copies on my machine and seems to work fine

    understood that no changes are made to the file structure - just changes in scripts, forms, etc.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    #2
    RE: updating remote programs

    That should work. If I understand correctly you dont need to reindex separately from the database compact. The compact should reindex all tables on it's own. Not that reindexing would hurt anything, just redundant.
    There can be only one.

    Comment


      #3
      RE: updating remote programs

      Martin, I would avoid copying your local *.CDX tables to the remote location, as well as the *.DBF and *.FPT files you already mention.

      It's my understanding the definitions for your tags in each index file are stored inside the CDX file along with the index itself. If you've modified your index definitions on the local machine, and then copy it on top of the remote set of definitions, the remote re-index will use the new definitions. This may not be what you want.

      -- tom

      Comment


        #4
        RE: updating remote programs

        thank's
        well - i'm really really really glad you told me that -
        now i have the option of changing or not changing the index definitions on the remote machine

        the support with alpha exceeds anything else i've ever seen
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        [email protected]

        ____________________
        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

        Comment


          #5
          RE: updating remote programs

          Code:
           testtest1test2
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            RE: updating remote programs

            [code] testtesttest
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment


              #7
              RE: updating remote programs

              Martin, one other thought. If you compact the remote database I believe this will pack the tables, causing records marked for deletion to be physically removed. A reindex would not do this. It should not be necessary to compact the remote database just because you've updated it's layouts, reports, and forms.

              -- tom cone

              Comment


                #8
                RE: updating remote programs

                You're all on target.

                If you modify forms, etc. related to a table, you need to send the DDD, DDM and DDX.

                For a set, send the SET, SEM and SEX

                If you make changes to the database itself, e.g. the scripts on the "code" tab, you need to send the ALM, ALX and ALB.

                When I send these data dictionaries to clients (almost every day) I don't bother with the remote database compact, etc. But I often will run a DDD maintenance routine before I send the dictionaries to help make them as clean as possible.

                - Steve
                -Steve
                sigpic

                Comment


                  #9
                  RE: updating remote programs

                  Martin,
                  I use PCAnyWhere to update programs at 2
                  locations: I use a DOS program.

                  I created a batch file called update.bat
                  and it does the following:

                  PkZip -a update *.ddd
                  PKZip -a update *.ddn
                  PkZip -a update *.ddx
                  PkZip -a update *.sex
                  PkZip -a update *.set
                  PKZip -a update *.sem
                  PKZip -a update *.adb
                  PKZip -a update *.alm
                  PKZip -a update *.alx
                  PKZip -a update header.*

                  If you are familiar with PKZip and PKunzip you will notice
                  that a file update.zip is created. (All locations have the
                  PKZip and PKunzip on them) I then transfer the update.zip to
                  the remotes and then unzip them. There is no need to update
                  the indexes for them. I have index, pack, delete buttons
                  all over the program so they really don't have to do anything.
                  My exit buttons pack and updates the indexes for them. I
                  learned the above from Tom Cone file on Learn Alpha, Never
                  could get his windows version to work for me so I converted
                  it to the DOS version of PKZ.

                  Jerry

                  Comment

                  Working...
                  X