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

Too many Versions

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

  • Too many Versions

    I wasn't quite sure where to put this .. so here goes.

    I have versionitis. I have Version 5 Devel with unlimited runtime package and about 50 clients on it. Works fine. Have done a lot with it.

    Then I got version 7 and wasn't motivated to port everything over so just played with the new features.

    Then I bought eight and just when I was ready to buy the runtime for it I got wind of version 9. Did I buy that. Yup..the whole package with server.

    So now I'm sitting here with version 9 and would like to start using it with the old A5 databases that are still serviced by the A5V5 runtimes. I don't doubt that I can successfully work with the A5V5 tables..I've tried that offline. But I didn't want to corrupt my data so I was careful about that.

    Can I use the Version 9 product with the old V5 tables while the V5 tables are still being used by the V5 runtime users without suffering any corruption? I probably will update the V5 Runtime users--but I have 50 to do and that is daunting.

    Any speculation about this?

  • #2
    Re: Too many Versions

    I don't see any reason you couldn't do this, but I would test it first.
    One thing I would not do would be to change any of the field rules or scripts in V9 until after you put them all in V9. I'm not sure if there have been any changes to the table and field rule editors and/or how they store the info in the dictionaries, which could cause major difficulties.

    Just out of curiosity, why would you want to do this?
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    martin_w_cole@msn.com

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

    Comment


    • #3
      Re: Too many Versions

      Reasons I'd do this..

      I need to put the runtimes on the client machines--there are about 50 of them and I doubt that I could do this very quickly. Probably take a couple of weeks.

      If I could make it instantly happen all across the network, I'd just go for it after backing up.

      Comment


      • #4
        Re: Too many Versions

        It's a bit late but, for anyone else reading this, don't change ANYTHING in v9 and expect it to work in v5.

        (I'm not sure if that's the case here or not. If you simply want to install v9 runtimes to access the same v5 app without changing anything in the application, that's not a problem. However, if you update the app at the same time, that IS a problem.)

        If you have xbasic scripts or functions, those can be changed as much as you want AS LONG AS you do not use any functions that don't exist in v5. (And if that's the case, why are you updating it?) Obviously, a new function that came out in v6 or later isn't going to work in v5.

        Also, a layout (form, report, etc.) edited in v9 might still work in v5 but there is also a very good chance that it won't. And if it doesn't, the only way to get it working again is to restore from a previous backup. Once a layout is edited in a later version, it may not be editable in the previous version anymore. It might still work but I'd never want to take the chance on a live application.

        Your best bet when upgrading to a later version is always to make a complete copy of the original, make all necessary changes, test it, then deploy the updated version. Trying to use a "hybrid" system to work in an older version while updating with a newer version is a recipe for disaster.

        Comment


        • #5
          Re: Too many Versions

          Hi Cal,

          I'll add one other gotcha with Action Scripts, that does not happen with functions and Script code.

          If you open Action Scripts for editing, when they are saved (even if no changes were made), the xbasic code that makes it up is regenerated. The code generated by an older version may be entirely different from that for a later version!
          Regards,

          Ira J. Perlow
          Computer Systems Design


          CSDA A5 Products
          New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
          CSDA Barcode Functions

          CSDA Code Utility
          CSDA Screen Capture


          Comment

          Working...
          X