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

Runtime Issue

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

    Runtime Issue

    I'm running 5 users on a network. The primary purpose of the app is to copy data from an SQL DB to its own tables and run reports.

    When using the network optimized function (with shadow), should the processes be pointing to the data in the shadow folder or the network shared folder?

    I keep the copy of the data on the shared folder and don't want the users to re-extract it unless they need to (date since last download, etc.). Therefore, I've been using the shared folder location for all functions.

    Since I want them to share data, would I be better off not using the shadow function?

    We are experiencing some delays in opening the database. A5 loads up quick from the workstation, but the db on the shared folder will take anywhere from 1-2 seconds to minutes before loading. We are looking into disk resource issues, but was wondering if anyone has had a similar problem.



    Another thing i've noticed. When using the copy method, if run on the developer version duplicate field names are saved differently (ie. Name, Name1, Name 2; ID1, ID2, ID3) while the runtime uses a different truncation (i.e. Nam0, Nam1, Nam2; ID, I0, I1). I've had to test the fields before changing. While this is always a good idea, I was surprised at how it was handled differently.

    #2
    Re: Runtime Issue

    If you use the shadow, not all data is extracted from the master database to the workstation, the data itself remains there. What is extracted are data that is used to create screens, forms, reports etc etc in order to save data transmission and thus time. Your data is never going to be on the client, it will be locked on the master during use on recordlevel and released after the user has left the record. Does this help you?

    Comment


      #3
      Re: Runtime Issue

      That's how I understood it.

      I've designed it so all intermediate extract tables remain on the shared server. I have all users now pointing to the shared db for everything. Am I taking a performance hit? Would I gain much from going back to the shadow?

      Comment


        #4
        Re: Runtime Issue

        The major benefit to shadowing is that the layouts associated with a database are copied to the local machines and loaded from them. If you have complex forms and reports and the users switch often, shadowing can help.

        In these days of gigabit switches, probably not as helpful as it once was.
        There can be only one.

        Comment

        Working...
        X