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

Ultra slow database changes in A4V7 on XP

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

    Ultra slow database changes in A4V7 on XP

    Been running A4V7 for years on 98, but recently switched to an XP box. When entering A4 or when changing databases/sets, system virtually stops for 30 to 120 seconds, then eventually continues. Have played with BIOS to kill the "A drive clatter". Although A drive stopped clattering, delays remain. Hard drive is super quick on non-A4 actions and is fast once the intended A4 database is finally reached. Any ideas? Thanks in advance.

    #2
    Re: Ultra slow database changes in A4V7 on XP

    Virus protection different? Can usually set to ignore the database directories.
    There can be only one.

    Comment


      #3
      Re: Ultra slow database changes in A4V7 on XP

      Thanks. This is a good idea and I did check with my admin. staff. They said our virus protection would not concern itself with the database changes within A4. Also, we have been running A4V7 in XP on another box for about 18 months. Have not had the same problem.

      Comment


        #4
        Re: Ultra slow database changes in A4V7 on XP

        Originally posted by BAND1T View Post
        Also, we have been running A4V7 in XP on another box for about 18 months.
        Good, then you have a working model to compare the differences with...
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


          #5
          Re: Ultra slow database changes in A4V7 on XP

          Good point. Just have not seen any differences yet. CONFIG.NT is set the same as are properties of ICONS that launch the apps. Concern is that somehow the drive is confused. Loading of A4 and data was done by copying by a share set up on 98 box, maybe something went wrong. Think next step is to copy the data directories and A4 program to a network drive, wipe A4 from the PC, then re-copy back. If that does not work, I will copy the data changes back to 98 box, wipe the 98 of all but the operating system, and then try again. Just hoping someone had a "magic pill".

          Comment


            #6
            Re: Ultra slow database changes in A4V7 on XP

            Is the directory structure of where the A4 data/application is the same on both machines? 98 & XP that is slow...
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #7
              Re: Ultra slow database changes in A4V7 on XP

              Not quite. The well running XP box runs from C:\ALPHA, the "slow XP" box runs from D:\ALPHA, the 98 box ran from D:\ALPHA. The directory set up on the 98 box and the slow XP box are identical. The path environment in XP includes D:\ALPHA on the slow XP box, but path is likely not needed since all BAT files leading to an A4 APP are pointed at the correct drive.

              Comment


                #8
                Re: Ultra slow database changes in A4V7 on XP

                I think I may have stumbled into the cause of the problem and the solution. To make A4 always open when requested, we made Winagent part of the startup of XP. I recalled that we did not have the slow database change problem before we made the Winagent change. Also, our other PC running A4on XP did not start Winagent at startup.

                As a desperate attempt, I looked at A4START1.BAT and A4START2.BAT I changed the lines below in A4START1.BAT from:


                rem start winagent "|path=spool|delete=yes|keep_req=no"

                winagent "|path=spool|delete=yes|keep_req=no"

                to:

                start winagent "|path=spool|delete=yes|keep_req=no"

                rem winagent "|path=spool|delete=yes|keep_req=no"


                The solution seems counter intuitive, but so far it seems to work and we can still have Winagent initiate at XP startup. We run scripts based on files received on our FTP server, so it is critical that A4 start each and every time. having Winagent up makes this possible. Without it up in advance, sometimes A4 will not start.

                Thanks for the thoughts on my problem.

                Comment


                  #9
                  Re: Ultra slow database changes in A4V7 on XP

                  Final wrap up for me on this. My solution of changing A4START1.BAT was just coincidental. The real problem turned out to be caused by faulty connections to other drives on our network. If any drive the PC is mapped to is not visible to the A4 PC, A4 slows to a crawl when database changes are requested. This is true even when the drives have absolutely nothing to do with the A4 application (and they don't). I have done enough testing back and forth to know this is the problem and can solve it.

                  Comment


                    #10
                    Re: Ultra slow database changes in A4V7 on XP

                    Barry

                    Wow.. Thanks for the update and glad that you solved it.

                    Maybe it'll help the next user that faces the same issue..
                    Al Buchholz
                    Bookwood Systems, LTD
                    Weekly QReportBuilder Webinars Thursday 1 pm CST

                    Occam's Razor - KISS
                    Normalize till it hurts - De-normalize till it works.
                    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                    When we triage a problem it is much easier to read sample systems than to read a mind.
                    "Make it as simple as possible, but not simpler."
                    Albert Einstein

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment


                      #11
                      Re: Ultra slow database changes in A4V7 on XP

                      To be honest, I should have figured this out earlier. When we moved to XP, I noticed A4 had the annoying habit of "chattering the A drive", a problem not present on 98. This should have told me that A4 has to check all the drives as it changes to a new database or set, even if the new database is on the same drive as the last. Also, whenever there was more than a single network drive disconnected, the delays became much longer.

                      Comment

                      Working...
                      X