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

V10 and V11 Developer on same machine

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

    V10 and V11 Developer on same machine

    Can you or should you run both V10 and V11 developer on the same computer. Are there any known issues with this?

    Thanks,
    tom
    Tags: None
    #2
    Re: V10 and V11 Developer on same machine

    No issues that I'm aware of. Currently I run v7, v8, v9, v10 & v11 developer + some RTs all on the same machine.
    Peter
    AlphaBase Solutions, LLC

     [email protected]
    https://www.alphabasesolutions.com

    Comment

      #3
      Re: V10 and V11 Developer on same machine

      Hi Peter,

      Thanks for responding. I am having an issue with a V10 application moved to V11 where the Java script and some X-baisic is not firing. Moving the same code back to V10 app server and everything works fine. I'm trying to understand what broke in the application and wanted to confirm if there were any corruption issues perhaps on having two different development environments on the same system.

      tom

      Comment

        #4
        Re: V10 and V11 Developer on same machine

        Originally posted by Peter.Greulich View Post
        No issues that I'm aware of. Currently I run v7, v8, v9, v10 & v11 developer + some RTs all on the same machine.
        Hi Peter;

        I have a few questions relative to how you maintain applications with multiple versions of a5 installed...
        (I know this is the web side of a5, but having seen your post here, I thought I'd just ask my question here, as most are still relevant.)

        Having multiple versions on your PC, what's the deciding factor of whether you keep the apps in the older versions, or whether you bring them current? (I'm guessing you use the: "If it's not broke, and no new work (needing new features) needs to be done, leave it where it was" strategy?)

        There must be some "logical criteria" that makes sense... Plus, I'm sure you've taken many of your older apps, and just said: "Hmmmm, lets see what happens when I open one up in this newer version of a5." ~ How does that usually turn out? (And how much of a process it to upgrade a finished desktop application?) (Assuming the version of a5 you upgrade to is at least 6 months old, so you're relying on a "fairly clean" a5 application?)

        I have all sorts of versions too, but very little to show (In terms of development) for the prior ones. That being said, what's the point of keeping more than maybe 1 version back or so? ~Unless, of course you expect to do work on older databases, originally developed by someone else (with older versions of Alpha)...... ???

        PS: I remember in the older print documents, like version 5, 6, and even 7 (spiral bound materials)....... That (desktop) examples indicated old ways and new ways of doing things. The way the material were written I was frequently "left to believe" the newer versions accomplished things differently, and thus the older methods (X-basic examples) would not necessarily work in the newer versions of a5.

        While I can understand this the opposite way around (newer code not working on the older versions).... The other way around (newer versions not able to handle the "ways of the older versions") always left me with concern. How much actually breaks when moving a (desktop) application forward, and what are the significant pitfalls you typically encounter? ~ Honestly, this is probably one of the reasons I waited so long to commit to a5. (and consequently "travel down an alternate path" for quite some time)

        I may be overly hopeful, but: My present thoughts are that a5 (desktop side anyways) is a fairly mature product, and thus is much more "forgiving" these days, in terms of working with older code & databases....

        ~Thanx in advance!
        Last edited by SNusa; 02-07-2012, 02:07 AM.
        Robert T. ~ "I enjoy manipulating data... just not my data."
        It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
        RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

        Comment

          #5
          Re: V10 and V11 Developer on same machine

          Robert,

          Right - "If it's not broke, and no new work (needing new features) needs to be done, leave it where it was" strategy?)

          I don't upgrade an app unless there is a specific need to. Clients don't want to pay for it unless they need certain new features. But generally, for me at least, desktop upgrades have been fairly painless.

          That being said, what's the point of keeping more than maybe 1 version back or so?

          Because I have clients that still user older versions. I also have personal apps that run desktop v8 for example. No need to "upgrade" them either.

          ~Unless, of course you expect to do work on older databases, originally developed by someone else (with older versions of Alpha)...... ???

          And that too.

          For the most part, Alpha is generally backwards compatible, including xbasic.
          Peter
          AlphaBase Solutions, LLC

           [email protected]
          https://www.alphabasesolutions.com

          Comment

          Previous template Next
          Working...
          X