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 database network problem

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

    Shadow database network problem

    Hi all.

    I have a standalone, non-Alpha application which uses .dbf tables. I've used Alpha5 v5 to create a new reporting application using the existing data by Adding these non-Alpha .dbf tables to the Alpha5 database, then creating the required queries and reports. It works great :)!!

    Now, the client has decided that they'd like to access the reports over a local, peer-to-peer network. Try as I might, I can't get the shadow database to properly point to the networked tables. Everytime I try to open a report, I receive an error that The system cannot find the file specified with an absolute reference to a path on drive C:, not my networked drive S:. I've followed the instructions in the Help and searched the forum to no avail. Here are the particulars:
    1. Network drive is mapped as S:
    2. Data resides on S:\DrH\Data
    3. Alpha5 runtime resides on C:\Alpha5Runtime
    4. Shadowed application and shadow tables reside on C:\Alpha5Runtime\shadow\hv

    Is there a way to resolve this? Is my problem related to the fact that the tables were Added to the Alpha5 database? Is there a way to change the paths in the shadowed database to point to S:? Any advice and assistance would be appreciated.

    Thanks.
    Michael Klein

    #2
    RE: Shadow database network problem

    Is your database so large that it really needs to be shadowed?? Can your customer live with a slight speed delay? Have you tried the application NOT shadowed?

    My first suggestion is to remove the shadow and point yourself to the networked path. If it runs, then you at least know that the pathing is not a problem.

    The only other possible problem is that these are not Alpha 5 tables, and the shadow routine doesn't know how to handle them.

    Tom

    Comment


      #3
      RE: Shadow database network problem

      Are the DBF tables in a folder other than the folder that contains your Alpha Five database application files? If so, Alpha is hardcoding the physical path to the data tables, and this is passed on to the shadow databases on each workstation. This might explain why the shadowed application is looking for the tables on Drive C:

      -- tom

      Comment


        #4
        RE: Shadow database network problem

        Tom,

        You hit it right on the head! The .dbf files were in a different folder than the Alpha 5 database application files. I moved everything to the same folder and all is now right in AlphaLand :).

        Thanks.
        Michael

        Comment


          #5
          RE: Shadow database network problem

          Tom,

          Trying the application "non-shadowed" provided the clue as to what was going on. Specifically, in the tables were greyed out in non-shadowed mode. That indicated that pathing was definitely a problem. I did what Tom Cone suggested and everything works fine now.

          Thanks.
          Michael

          Comment

          Working...
          X