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

Synching data between VPS and local server

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

    Synching data between VPS and local server

    We have a web application that allows our users to update their user information. We also have a local server that contains the same user information that we update if the user calls us and wants us to change it.

    We need to synch the data between our local server and our VPS data. We have a routine to do this but were trying to identify a way to access the data on the VPS directly without using FTP to upload a change file.

    It would be far more convenient to change the record on our VPS at the same time we changed it on our local drive. Is this possible?
    John J. Fatte', CPA
    PRO-WARE, LLC
    Omaha, NE 68137

    #2
    Re: Synching data between VPS and local server

    What database are you using? If just the dbf files I don't know of one off hand but if your using more of an enterprise solution then I know it can be done. You would have to contact you dB vendor to find out about two way replication and how it is done for your dB

    Joe
    Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

    Comment


      #3
      Re: Synching data between VPS and local server

      I just googled two way replication for dbf files and found:

      http://software.techrepublic.com.com...x?docid=681597

      Might help.

      Joe
      Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

      Comment


        #4
        Re: Synching data between VPS and local server

        Originally posted by cavj1 View Post
        I just googled two way replication for dbf files and found:

        http://software.techrepublic.com.com...x?docid=681597

        Might help.

        Joe
        Thanks for the reply and the link, but I think they are out of business. Never could get to a website for the company that created this application. Most recent info about it is 2002.

        And yes, we are using dbf's.
        John J. Fatte', CPA
        PRO-WARE, LLC
        Omaha, NE 68137

        Comment


          #5
          Re: Synching data between VPS and local server

          Here is what we've come up with so far. It's not pretty, but we think it will work.

          When we make changes on our desktop (in office) app to our server, we will post the changes to the customer record and to another file that we call our "changes" file. We will also create another file that will serve as a flag to indicate that there is changes in our "change" file.

          We are then going to create an application that will run on our web server that will simply use FTP to check to see if our flag file exists. It will do this every 15 minutes. If the flag file exists, it will copy the changes file to the server and update the appropriate file on the server with the changed records. It will then erase the flag file on our local server using FTP.

          The next time we make changes on our local server, it will check to see if there is anything in the changes file and change a logical field for all the existing records to indicate that these have been transferred to the server and the changes recorded. It will then add new changes to the file and create the flag file.

          We will do something similar to this going the other way if one of our users changes a their information on the server.
          John J. Fatte', CPA
          PRO-WARE, LLC
          Omaha, NE 68137

          Comment


            #6
            Re: Synching data between VPS and local server

            John,

            Do a search in the message board for directory watch (or maybe just watch) for a way to make your process more automated.

            Pat
            Pat Bremkamp
            MindKicks Consulting

            Comment


              #7
              Re: Synching data between VPS and local server

              Thanks Pat. I'll see what I find.
              John J. Fatte', CPA
              PRO-WARE, LLC
              Omaha, NE 68137

              Comment


                #8
                Re: Synching data between VPS and local server

                Originally posted by Pat Bremkamp View Post
                John,

                Do a search in the message board for directory watch (or maybe just watch) for a way to make your process more automated.

                Pat
                Pat

                I found the post you were referring to and the built in function file.watch. I also found a reference to a program called Watch Directory at www.watchdirectory.net.

                There is a problem with both of these and this explains the methodology that we selected. The file that is getting updated on the local server is about 3-4 MB and we are concerned with the time it will take to copy the file. Hence, we created a change file that will just contain a copy of the changed records. This will probably be fewer than 30-40 at a time. With the change file being that small we can afford to copy it every 15 minutes, and this is key for us. Our users will be accessing our web server app to validate their applications as well as order upgrades.

                Here's an example of why we need to update so quickly. A user calls us and places an upgrade order over the phone. They can download our demo and then with the provided activation code, they can activate their software immediately and have the full version. However, our user file on the web server needs to be updated to show that they have purchased the app; otherwise, they won't be able to activate.

                It needs to be seamless and happen fairly often otherwise we get phone calls. Lots of them. We have over 20,000 users who upgrade every year.
                John J. Fatte', CPA
                PRO-WARE, LLC
                Omaha, NE 68137

                Comment


                  #9
                  Re: Synching data between VPS and local server

                  re:
                  We have a web application that allows our users to update their user information. We also have a local server that contains the same user information that we update if the user calls us and wants us to change it.
                  I don't understand why you have a local version, why isn't everything just on the VPS? - Why don't you just make the requested changes directly on the VPS?
                  Insanity: doing the same thing over and over again and expecting different results.
                  Albert Einstein, (attributed)
                  US (German-born) physicist (1879 - 1955)

                  Comment


                    #10
                    Re: Synching data between VPS and local server

                    John,
                    I'm working on something with a similar need.
                    -
                    The way I intend to solve it is via using Logs
                    -
                    Eg on the Web server a change is made, this change is logged and an FTP log file is sent to the local server, The log file is processed and then the updates are made. The Log is made of 3 Parts, Modifications, Insertions, deletions
                    -
                    And exactly the same from the local server to the web server.
                    -
                    Because of the nature of our data I can afford to risk optimistic locking of records.
                    -
                    This system I'm actually working towards making my own cluster server, as I can't find anything on the market to do this.

                    Comment


                      #11
                      Re: Synching data between VPS and local server

                      Originally posted by peteconway View Post
                      re:

                      I don't understand why you have a local version, why isn't everything just on the VPS? - Why don't you just make the requested changes directly on the VPS?
                      Peter

                      That would be ideal if everything was just run from the web, but the desktop app was created about 4 or 5 years ago and the web app was just created in the last couple of months - primarily so our users could place upgrade orders instead of mailing or calling us. The desktop app is much more robust than the simplicity of the web app and it will take a year or so to refine the web app to contain all the features we have in the desktop app.

                      Eventually, everything will be on the web.
                      John J. Fatte', CPA
                      PRO-WARE, LLC
                      Omaha, NE 68137

                      Comment


                        #12
                        Re: Synching data between VPS and local server

                        Originally posted by ColinJD View Post
                        John,
                        I'm working on something with a similar need.
                        -
                        The way I intend to solve it is via using Logs
                        -
                        Eg on the Web server a change is made, this change is logged and an FTP log file is sent to the local server, The log file is processed and then the updates are made. The Log is made of 3 Parts, Modifications, Insertions, deletions
                        -
                        And exactly the same from the local server to the web server.
                        -
                        Because of the nature of our data I can afford to risk optimistic locking of records.
                        -
                        This system I'm actually working towards making my own cluster server, as I can't find anything on the market to do this.
                        Sounds very similar to what we are trying to accomplish with our "change" file. Rather than make it realtime, we decided that if we sync'd every 15 minutes, that would be good enough.
                        John J. Fatte', CPA
                        PRO-WARE, LLC
                        Omaha, NE 68137

                        Comment

                        Working...
                        X