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

About to upgrade Client to steps?

  • Filter
  • Time
  • Show
Clear All
new posts

    About to upgrade Client to steps?

    I have taken a very old A5V1.04 application and converted it to A5V11 (with many kudos to Tom Cone) and I am now just about ready to upgrade and install on the client's machine. I currently have their original DBF, DDD, DDM, DDX, and CDX files, which have been updated in my V11 application.

    Since they will have added more data to their database over the past month, I'm thinking that once I have the new app on their machine (in a new folder), I can then copy their newer DBF file to this new folder. I would think the only thing I would need to do at that point is re-build the indexes.

    Should this work? Or do I need to do a fancier method of importing and apending their data from their old DBF file to my new DBF file?

    Thanks for any recommendations.


    Re: About to upgrade Client to steps?

    Overall, yes, this should work, but you should have full backup sets of course, and try one or two to confirm before you do 'em all.

    One hitch: The memo field storage type changed between v1 and v11. So for any table you're transferring that has a memo field, an append is your best option.

    Test, verify, repeat.


      Re: About to upgrade Client to steps?

      Nice, and thanks for the response. I have all char, numeric and date fields , so I should be good there.

      Forgot about the sets though:

      I have the SEM, SET and SEX files but since there's no "real" data in these I'm thinking I don't want to copy any of their old files to the new folder. I will of course re-build all the indexes after I've copied the DBF files though. I hope I'm OK with this also.
      Last edited by John Graves; 08-23-2013, 12:35 PM.


        Re: About to upgrade Client to steps?

        Not sure. The SEM file is a memo file with a different extension, and as I noted, memo-file-types have changed.

        (Note -- I could be wrong here and maybe someone else can verify. I'm having doubts that maybe my recollection is that memo file types changed in Alpha Four, but have been constant ever since. Just haven't worked with this older stuff for a very long time.)

        The drawback to your suggestion is that if any of the reports or forms are tied to the SET, you'd lose them too and have to re-create. I say try a straight-up transfer to see if it works before you create possibly unnecessary work for yourself.


          Re: About to upgrade Client to steps?

          Originally posted by Steve Workings View Post
          (Note -- I could be wrong here and maybe someone else can verify. I'm having doubts that maybe my recollection is that memo file types changed in Alpha Four, but have been constant ever since. Just haven't worked with this older stuff for a very long time.)

          An A4 memo file is .dbt while A5 is .fpt

          I don't remember a change during the course of A5 versions.

          But those darn versions 1 and 2 are such different birds...

          Personally I've rebuilt anything that old in the targeted version.

          And I agree with your previous post - append the data rather than replace the files....
          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


            Re: About to upgrade Client to steps?

            I just did an upgrade from v8 to v11 and always suggest doing appends rather than file copies. Less chance of something I did getting changed. If dbf's were not changed in any way and you do not copy supporting files that have the forms, reports etc in them, then a copy should work.

            Like Al, I don't think there was any change in memo as long as they both have the same extension.


              Re: About to upgrade Client to steps?

              If you have introduced any new, or changed any existing, field rules as part of the upgrade, you can sometimes get a surprise when appending data. For example, autoincrement rules and validation rules can be problematic if the incoming data is not perfect. If you run into this, you might consider removing the field rules from a problem table(s) prior to the append and restoring them afterwards. You can do this with the Copy Utility I uploaded to the Code Archive. It would be considered a "last resort" option and make sure you have a backup from which to restore the rules after deletion.


                Re: About to upgrade Client to steps?

                It was fun to do taking 13000 records in an essentially flat file with one entry being as much as 14 times due to people at that company and moving the app to 1 company(bad spellings and all). It dropped almost 3000 records in the company part and the contacts are 1-m on that. Also had to move other stuff out of that big table. Compound that with 5 memo files and the errored fpt file at 1.8 gigs, it was a nightmare. Then the shortening of file/field/index names. All the connecting fields were character and different lengths-now all numeric and same length.

                Point - there was no way to copy dbf's.

                Any how, 33 appends and other later with lots of code in them and other stuff along the way like 18 temp sets. It works. Probably was easier ways to do it, but they should have no problems for at least 10 years.