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

Shadow Db

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

  • Shadow Db

    I have a program that I have previously deployed in version 8 on a server with the ten user runtime license. My clients have several systems on which I installed the runtime and made a shadow copy. That has worked well up to now.
    I have now purchased version 9 platinum, made some upgrades to the database and am planning on upgrading the client's server and client systems. I was told by tech support that I dont' need to have the runtime installed on the server, just locate all the files on the server and install the runtime on the client machines, connecting to the server. The problem I foresee with this is that I would then have to run an update on every single system whenever I make a change, instead of having the shadow copy detect the newer version number and run and update with each new startup,, if needed.
    So my question is this. Am I correct about this? And if so, will I have any licensing issues if I install the runtime on the server and each of the clients?

    Another question (probably suited for a completely different thread) is... should I encrypt the files if I need to ensure security? I'm concerned about issues with encryption that I may run into down the road.

    Thanks,
    Joe

  • #2
    Re: Shadow Db

    Originally posted by jgodfrey View Post
    I have a program that I have previously deployed in version 8 on a server with the ten user runtime license. My clients have several systems on which I installed the runtime and made a shadow copy. That has worked well up to now.
    I have now purchased version 9 platinum, made some upgrades to the database and am planning on upgrading the client's server and client systems. I was told by tech support that I dont' need to have the runtime installed on the server, just locate all the files on the server and install the runtime on the client machines, connecting to the server. The problem I foresee with this is that I would then have to run an update on every single system whenever I make a change, instead of having the shadow copy detect the newer version number and run and update with each new startup,, if needed.
    So my question is this. Am I correct about this? And if so, will I have any licensing issues if I install the runtime on the server and each of the clients?
    You are NOT correct. Any updates you make are to the database on server--no version of Alpha Five needs to be on the server at all. Let's say you make changes to a report in the Db and transfer those changes to the DB on the server (copy over a new .DDD file) and upped the version number by also transferring a new .ADB (and maybe .ALM and .ALB) file (or just upping the number remotely IF you had the full version on the server). Your workstation based runtime Shadow DB's detect that change and automatically update, presuming you have things set to do this.

    Where you would run into the kind of issue you raise is with runtime patch updates. They have to run on each workstation, but this is not a big deal unless you, like some others, want to make it a big deal. Users can download the patch either from your web site or from Alpha's and just run it.

    Originally posted by jgodfrey View Post
    Another question (probably suited for a completely different thread) is... should I encrypt the files if I need to ensure security? I'm concerned about issues with encryption that I may run into down the road.
    I suppose encryption depends on the nature of your application and what it is you might be worried about. I have never found encryption necessary but your case may be different. Are you worried about data or just program code? There are ways to setup some security for your program code (see Help file or search this forum). As for data files, gee, just be sure it is really necessary as it probably has overhead and possibly other negatives--I don't really know. Again, searching this forum for "encryption" might help.

    Raymond Lyons

    Comment


    • #3
      Re: Shadow Db

      Hi Raymond:
      Sorry to budge in .... but I have a related question:
      Originally posted by Raymond Lyons View Post
      ..and upped the version number ...Your workstation based runtime Shadow DB's detect that change and automatically update, presuming you have things set to do this.
      Is it possible to get A5 to automatically update the shadow DB on startup without having to increase the version number each time you modify the master DB on the server? Thanks

      Comment


      • #4
        Re: Shadow Db

        Gaby,

        Well, the shadow has to have some way of knowing that changes have been made. Alpha's way is to up the application version number in the .ADB file (or one of those .A** files). I suppose you could have a detection scheme work some other way. For example, I guess you could create a text file with version numbers in it, up that and transfer that file with your other changes to the server DB. Then in the autoexec check that text file or maybe just check to see if the text file has changed (date modified) and if so put code in the autoexec that refreshes the shadow "automatically" on startup. I suppose there are other ways also. But obviously there has to be some way for the shadow to know it needs to refresh. And yes, there can be problems with have to transfer .ADB files, especially if using the built-in secuity/logon sysem, but there are also ways to deal with that too.

        Raymond Lyons

        Comment


        • #5
          Re: Shadow Db

          Thanks Raymond - I'll make easy on myself, increase the version# and let A5 do the rest.

          Comment


          • #6
            Re: Shadow Db

            Thank you Raymond. That's good to hear. So I kind of get it now. As long as the version number changes (and that is reflected in the adb file) then the shadow db's will detect that and update.

            And I think I'll stay away from the encryption for now. I worry that anyone with access to the server could copy and use the dbf files. The data that is being stored is very confidential and would be a violation of HIPPA regs if it were to be compromised. But I suppose if my client has strong secutity set up for the server I'd be okay.

            Thanks again,
            Joe

            Comment

            Working...
            X