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

Ability to "clone" a workspace with a new name....

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

    #16
    Re: Ability to "clone" a workspace with a new name....

    Terence,
    Turns out the initial problem I had was due to an expired SQL password. See post # 3 in here

    Comment


      #17
      Re: Ability to "clone" a workspace with a new name.... Lessons Learned

      This was a good exercise and here are my "Lessons Learned... on how to clone a project"

      - Run the clone batch file provided by Steve Wood (must have same source folder & project name)
      - Delete all the security files in the cloned folder
      - Setup the new connection string if using another database
      - Change all the paths in: Publish, project, phone gap profiles
      - Check/change ftp info
      - Change ALL connection strings in your code
      - Uncheck security - Save, Close and Reopen the project
      - Redo the security framework and confirm that all tables are created in the new database
      - Publish ALL files to the AA5 app server
      - Check cross-domain connection via telnet (this is where I spent the most time - simple but not overtly apparent)
      Using your VPS IP is no guarantee that calls made to the remote services are from that IP
      Test on VPS: telnet <remoteDB-IP> 3306 will fail and give you the correct IP needed for mySql remote access
      - General Comment:
      MSSQL is not case sensitive but mySQL is - so stick with a consistent naming convention if you plan to migrate databases
      - Test the app in a browser
      - Publish to Phone gap - check and recheck all settings
      - Test the mobile app

      If anyone has some more tips please post!

      Thanks to all the folks that take time to contribute to this body of learning and knowledge.

      Comment


        #18
        Re: Ability to &quot;clone&quot; a workspace with a new name....

        In most cases, just running 'step 1' is all you need, and maybe changing the target database. Likely the reason you find you have to delete/recreate your connection strings and security files is that you use a different connection string name for each of your projects. I have always used "conn" for the connection string name for every project I have ever built (there is no reason to use custom connection string name for each project, and it just make it more confusing if you do). The active link tables reference this connection string name, so if you change it, that would require rebuilding the active link tables (although not the actual database tables).
        Steve Wood
        See my profile on IADN

        Comment


          #19
          Re: Ability to &quot;clone&quot; a workspace with a new name....

          Steve; when I adopt new technology I want to make sure its sound... eg I'm a firm believer of 3-tier deployment scenarios: database & app isolation for performance, security and scalability. In this case I migrated the SQLServer database to MySql on another VPS. I had to prove to myself this was doable without any issues.

          It does not take long to recreate the security instance - I wanted to be safe rather than sorry if for any reason the original table on server A got overwritten unintentionally - that was enough reason to do this step.

          I have custom code so that meant changing all the connection strings in the code, the case sensitivity naming conventions came up - I spent some time trying to figure out why there were blank pages.

          My workflow may not be for everyone but if it saves someone 1-2 hours or more then its worth learning from someone else. I have to say this is a vibrant forum compared with others.

          I wish Alpha would invest in a mobile version of the forum - it would make things even more exciting! and productive too!

          Comment

          Working...
          X