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



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

Network Server Problems

  • Filter
  • Time
  • Show
Clear All
new posts

  • Network Server Problems

    I have a problem with alpha5 v4.5 build 266.

    One of my clients is using v4.5 on a network with runtime applications. The system has been installed for over a year with no problems. Now problems have been encountered when doing certain development on the server. Modifying the database design is ok but if you try to compress the database Alpha hangs. It has created a $$ file and seems to have started to write details back when it hangs. Updating indexes also causes Alpha to hang.

    If you copy the application to the C: drive and then carry out a compress and update indexes there is no problem.

    I have tried loading Alpha on to different PCs on the network but with the same result.

    Pcs have had Win 95/98 or 2000 installed and the server is running Novell 5. The only thing the client has said that they have done in the last 6 months is to start implementing Zen, they also have Contextless Log-ins

    Do you have an ideas what may be wrong.

    I am waiting agreement from the client to Implement Alpa5 V5 and that is likely to be in early January 2003. Is it possible the new version would have similar problems?


    Andrew sim

  • #2
    RE: Network Server Problems


    I wonder if it's a simple matter of conflict with open files? When you compact the database, Alpha has to acquire an exclusive lock on all the tables. If others on the network are using the app, I would not be surprised for the effort to compact the database to fail. For this reason, and because crashes during development are not unheard of, many would advise AGAINST doing development work on the machine which serves as the file server.

    -- tom


    • #3
      RE: Network Server Problems

      Thanks for the Email. I carried out tests this morning and there were no other users logged on to the server using the Database.

      Yes major design updates are not done on the server. Mods done on the server tend to be changes to reports. Having to always do mods elsewhere and then upload takes longer. My client tends to create new reports as and when needed and I carry out all major design changes.

      This problem is new, didn't exist 6 months ago. I have other clients where we use the same procedures without any problems.

      The client also mentioned that there was a prior problem, which I do not if it has been sorted, which they stated had something to do with "Timing" on the server and outside consultants were to review. The IT staff member .who mentioned this was on holiday today

      Andrew Sim


      • #4
        RE: Network Server Problems

        Andrew, if workstations on the network crashed while running an Alpha app, could the server still have active processes running that were orphaned? I wonder if rebooting the server is apt to be helpful ?

        Another idea, would be to load a new database on the server... say the Alpha invoicing app... run it from a Win 98 station, and then try to compact it from the server. If this runs ok, wouldn't that rule out system level problems on the two machines? -- tom


        • #5
          RE: Network Server Problems

          >>My client tends to create new reports as and when needed and I carry out all major design changes.

          This problem is new, didn't exist 6 months ago.


          • #6
            RE: Network Server Problems


            If you cannot compact the database on the server with no terminal attached or files open, that is a good indication that at least some of the data dictionaries are corrupted (or a file is open) Many people don't realise that when they modify a report, form etc, the old design stays in the data dictionary until it is compacted. If the user has been playing with their own reports for six months, this is likely a problem.

            One clue that this might be happening would be file sizes. Check the size of all of the .ddm and .sem files for the application on the server. If any are very large, like over a few meg in size, then that would probably indicate a problem. The only reason these files might even be that large is if there are a lot of complex reports or forms. The largest I have seen in my apps is about 2.5 meg after compacting. I have seen one data dictionary for a table with only one form and no reports at over 10 meg. That one was giving the user many headaches. After compacting, I think it was about 400K. There was a lot of junk there.

            Most developers either don't allow the end user to make any modifications or include some maintenance process to run compact periodically.



            • #7
              RE: Network Server Problems

              I saw something similar to this a while back and it turned out to be the Novell client software.There were a few machines that got an error when optimizing ahude app and others that didn't.The ones that had a problem had a different version of the Novell client software.You might experiment with one machine changing the client software and see if that helps.