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

Create shadow Db on each station

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

  • Create shadow Db on each station

    DO you have to run optimization from each workstation?
    or,
    Can I copy the shadow DB folder plus the icon to other workstations?
    Is there a better way to distribute the shadow db?

  • #2
    Re: Create shadow Db on each station

    Hi Mike,

    Are you doing the update/optimization locally, in the same office or building.

    Ed

    Comment


    • #3
      Re: Create shadow Db on each station

      Yes.

      Comment


      • #4
        Re: Create shadow Db on each station

        Hi Mike,

        I use the optimization by bumping up the version number under tools in the control panel after an application update. If it is the initial install I point runtime on each machine, at the the server with the updated total application that is in one folder on the server. Open up the application.
        Go back to the control panel and create a shadow database. Also I create the shortcut this way. You only have to do it once for the initial install. After that just bump up the version number, and make your pick as to how you want each station to update from there.

        I do not use a install program locally.

        You probably could do it your second way, by copying a proper shadow folder inside each workstation My Documents folder. And copying the icon to each desktop. I have not done it that way.

        I have another application, still on the company wan, that is probably 15 miles away still in version 7. On the server I have a development copy of the application. There are only 4 users there, and by locking them out, I do the updates on the server(they are shadowed). When I am finished doing the updates, I bump up the version number, and the updates are done by each workstation. I use Windows Remote Desktop conection, it is reasonably fast, to do what I need to do.

        Ed
        Last edited by Ed Barley; 10-26-2010, 12:36 PM.

        Comment


        • #5
          Re: Create shadow Db on each station

          Thanks for the response.
          Just one question:
          What is "bump up the version number"?

          Comment


          • #6
            Re: Create shadow Db on each station

            Hi Mike,

            You make up your own version number. Go to Control Panel, Tools, Network Optimize. Look at the attached JPG.

            Say you start with 4.569 as your version number. After you do some programming and want everyone to use your new efforts, make the version number 4.570. Look at the 3 radio buttons on the tab. I use "Warn the user" one.


            Ed

            Comment


            • #7
              Re: Create shadow Db on each station

              HINT: Look at the image in Ed's post above and note that the "Options" tab isn't really optional. Think of it as "Options that must be reviewed and set as necessary."

              Comment


              • #8
                Re: Create shadow Db on each station

                Thanks, I will try.
                I never realize that option.
                Thanks again.

                Comment


                • #9
                  Re: Create shadow Db on each station

                  We do it slightly differently. I create a "Master" shadow database on my machine. I then create a self-extracting zip file that is directed to unzip to the common shadow folder on every workstation. This file is in a shared folder on one of our servers. We keep a text file on the server with update version numbers (dates) for all of our different shadow databases. When the users boot their machines, a routine runs that checks the local version number against the version number on the server, and if the server is newer, it causes the zip to execute and therefore refreshes the shadow. Doing it this way, we don't run into the problem of multiple workstations attempting to do a shadow refresh at the same time.

                  Tom

                  Comment


                  • #10
                    Re: Create shadow Db on each station

                    "Don't run into the problem of multiple workstations attempting to do a shadow refresh at the same time."

                    I guess this issue of multiple DB optimization can occur.

                    That routine, is it proprietary?

                    At the present I do not have large deployment of any of my DBs.
                    But I can see that routine could be of great help.

                    Thanks for the response and the comments.

                    Comment


                    • #11
                      Re: Create shadow Db on each station

                      Mike,
                      No, it isn't proprietary. We use winzip to create the self extracting zip file, and a product called "Ground Control" to do the checking. Ground Control is a scripting language that will execute all sorts of DOS and windows commands without user intervention. We execute a "startup" routine when we boot the machines, and it does all sorts of checking, drive mapping, and other things that would be common tasks manually done. It is a godsend.

                      Ground Control is from Acrasoft. They have a website, and, most likely, a free trial.

                      Tom

                      Comment

                      Working...
                      X