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

Files to be copied on client database when an upgrade is made.

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

    Files to be copied on client database when an upgrade is made.

    What are the files to be copied or overwritten on a client database? If i made an additional forms,labels,table structures etc. I dont know what to overwrite if there are already records on client/customers database.
    Tags: None
    #2
    Re: Files to be copied on client database when an upgrade is made.

    Has been discussed many times here. Alpha Five File Types

    You don't send .dbf, .cdx, and .fpt files.
    There can be only one.

    Comment

      #3
      Re: Files to be copied on client database when an upgrade is made.

      Thank you Stan, sometimes i read and forgot to bookmark but could not find it coz i can't remember if i have seen in the other documentations, msgboard or alpha wiki, My apologies if i just post a thread to look for it.And with the your help and other alpha moderators, it's sometimes easier to just post the question, just like now that you immediately showed me the link.

      Comment

        #4
        Re: Files to be copied on client database when an upgrade is made.

        Originally posted by JetLi View Post
        ... it's sometimes easier to just post the question...
        Yes that's very apparent from the quantity and quality of questions you've asked.

        Please use the other resources that are available and don't wear out your welcome on the messageboard.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment

          #5
          Re: Files to be copied on client database when an upgrade is made.

          A quick related question. When you update with just the app files (no data files) is it necessary to Database Compact? I usually do. Am I wasting my time? ~ Tom

          Comment

            #6
            Re: Files to be copied on client database when an upgrade is made.

            Tom,
            I do and do not think I am wasting my time. Others will disagree.

            From Stan
            You don't send .dbf, .cdx, and .fpt files
            I do send the whole app sometimes(one of my main apps is always done this way). My application, on install, conditionally copies the old app to a save folder and then overwrites the whole app. An append is then conditionally run. By doing it this way, it does not matter if the table structure has been added to or if there is just a form/report/etc change.

            Remind you that I use astrum for my installs.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment

              #7
              Re: Files to be copied on client database when an upgrade is made.

              I don't disagree but I was answering the original question.

              If i made an additional forms,labels,table structures etc. I dont know what to overwrite if there are already records on client/customers database.
              I did not try to get into a discussion of all the possible things one might do.
              There can be only one.

              Comment

                #8
                Re: Files to be copied on client database when an upgrade is made.

                Originally posted by Tom Patten View Post
                A quick related question. When you update with just the app files (no data files) is it necessary to Database Compact? I usually do. Am I wasting my time? ~ Tom
                It's not necessary but I think it's probably a good idea. I even do it fairly often during development just to avoid the weird problems I, and others, have occasionally seen when a lot of development has been done without compacting.

                I have a routine that uses dictionary.update() and keeps track of files sizes before and after so I can see how much the file sizes have been reduced. Sometimes it saves a few hundred bytes and sometimes it saves a few megabytes. It's pretty hard to guess how much it will be but just editing an existing script won't mean much while deleting complex forms will.

                Comment

                  #9
                  Re: Files to be copied on client database when an upgrade is made.

                  If i made an additional forms,labels,table structures etc.
                  I'm thinking that changing of the tables presents a requirement beyond merely sending everything but the .dbf, .cdx, and .fpt files, possibly requiring A5_add_fields_to_table() and/or a5_changefieldsize()...etc.
                  Mike W
                  __________________________
                  "I rebel in at least small things to express to the world that I have not completely surrendered"

                  Comment

                    #10
                    Re: Files to be copied on client database when an upgrade is made.

                    Yes, (sorry Stan)I read it that table structures are part of it too. That is why my answer was to install all AFTER making sure there was a copy of the old tables and then append ther records to the new tables. It just made sense to do it that way.
                    Dave Mason
                    [email protected]
                    Skype is dave.mason46

                    Comment

                      #11
                      Re: Files to be copied on client database when an upgrade is made.

                      Originally posted by Mike Wilson View Post
                      I'm thinking that changing of the tables presents a requirement beyond merely sending everything but the .dbf, .cdx, and .fpt files, possibly requiring A5_add_fields_to_table() and/or a5_changefieldsize()...etc.
                      I came to think of it, What if there are additional fields on many tables? will i do it manually in every table before i copy all the other files of the database?

                      Comment

                        #12
                        Re: Files to be copied on client database when an upgrade is made.

                        This whole topic has been discussed many, many, many times. Also, try searching the threads for previous versions of A5. There's a ton of info out there already and, since most things in previous versions of A5 still work in the current version, searching the threads for other versions will often turn up the answer.

                        http://msgboard.alphasoftware.com/al...l=1#post583207

                        Comment

                        Previous template Next
                        Working...
                        X