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

Are Shadow files the same for Runtime & Developer License?

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

  • Are Shadow files the same for Runtime & Developer License?

    I am having some trouble getting a shadow copy to run correctly on my desktop. The other workstation with the runtime is working ok. I am thinking I can just copy her shadowed files to my computer... Would that work using the same directory structure?
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

  • #2
    Re: Are Shadow files the same for Runtime & Developer License?

    I decided to try it anyway - and it works! I deleted everything that was in that directory then copied the shadowed tables from the workstation.

    Before when I ran the Network optimization from the server's control panel I added the extra files and pointed it to create the shadow in the same directory on my C: drive. However when the routine opened the shadow - they were the wrong files.

    Updating the newly copied files to the new version worked correctly. Go figure.

    Thanks to Dave M. for the advice in my old thread
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


    • #3
      Re: Are Shadow files the same for Runtime & Developer License?

      Robin
      I do this all the time. As long as the structures are the same and the path to the server data are the same, you can copy/zip/use installer to duplicate to as many work stations as you need.

      My installs for clients include the server data files and a separate runtime and shadow copies with either a "bootstrap" or already set up if I know the name of the server and the data path. I simply create the shadow copy on my computer and then include it in the installer.

      Some of my clients have caught on to this now(with my help). New computer? They just copy a runtime over to the new computer. It is almost always up to date so not even a re-shadow.
      Dave Mason
      dave@aldadesktop.com
      Skype is dave.mason46

      Comment


      • #4
        Re: Are Shadow files the same for Runtime & Developer License?

        For some reason on a new shadow creation thru A5, it wants to put it in a directory named 'shadow' even if you tell it otherwise. I've had it happen before in past versions so I ought to know better. The update however works on the current path without a glitch. In the future I hope I remember this!
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment


        • #5
          Re: Are Shadow files the same for Runtime & Developer License?

          Yes, it is a pain to have to change it everytime.

          I believe you can just copy the whole thing to any folder and it should work.
          Dave Mason
          dave@aldadesktop.com
          Skype is dave.mason46

          Comment


          • #6
            Re: Are Shadow files the same for Runtime & Developer License?

            Originally posted by MoGrace View Post
            For some reason on a new shadow creation thru A5,
            I have moved away from using shadow databases but when I did, I never used Alpha's built in shadow creator for the very reasons mentioned above.

            It is much simpler to just create a blank adb file and give it the exact same name as the one for your app.

            Then just create the autoexe script in the blank adb file with code simpular to this.

            Code:
            dim master_db_name as C
            dim shadow_db_name as C
            dim startup as c
            
            a5.window_title = "T_six"
            a5.window_icon = "T-Six.ico"
            'Hide the Control Panel.
            :controlpanel.hide()
            
            master_db_name = ""
            shadow_db_name = a5.Get_Name()
            ui_modeless_dlg_box("Install T-Six",<<%dlg%
            {can_exit=exit}
            {lf};
            Specify the filename of the master copy of the application:;
            [%P=ui_get_file("Select file","(*.adb)",master_db_name)%.100master_db_name];
            {lf};
            <Click Here to Start Install!oK?.not.(master_db_name="")> <Cancel!cancel>;
            %dlg%,<<%code%
            if a_dlg_button = "cancel" then
                ui_modeless_dlg_close("Install T-Six")
                a_dlg_button = ""
            end if
            if a_dlg_button = "oK" then
                if file.exists(master_db_name) = .f. then
                    ui_msg_box("Error", "Master Database not found.")
                else
                    a5.Load(master_db_name)
                    a5_nopt_CopyAddFiles(shadow_db_name, master_db_name)
                    create_shadow2(shadow_db_name, .t., .t.)
                    ui_modeless_dlg_close("Install T-Six")
                end if
            end if
            %code%)
            When you start up with the blank adb file, it will then ask where the master is and will then build the shadow database. No mus, no fuss.

            Comment

            Working...
            X