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

Network problems ...

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

    Network problems ...

    I must be missing something very basic - my application works fine on my machine, but not on the network. For example, the user cannot enter a new record into the lookup table on the network, but it works fine on my machine. Is there special code that is needed to trap or avoid these errors??

    Gary
    Gary S. Traub, Ph.D.


    #2
    RE: Network problems ...

    A couple of questions,

    Is the folder in which the tables reside shared for full access?

    Did you create a different form that restricts functions for other users?

    Check your networking. We have a very robust (250 users, 5 servers, 9 hubs, 4 switches, etc.) network here, and after a lot of tweaking, it works fine.

    Comment


      #3
      RE: Network problems ...

      Tom:

      Thanks for responding. No, all have full access.

      Here is the specific problem thart my network users are running into. When in a form, they access a lookup table of referrers. When the user enters a new referrer and tries to save it, they get an error message "Not an open table."

      Gary
      Gary S. Traub, Ph.D.

      Comment


        #4
        RE: Network problems ...

        I remember something in the field rules that allows/disallows users from adding to or editing the lookup table. Could that be the problem?

        Otherwise, maybe some of the heavy duty v4 users could help.

        I am still using v1.02, but am trying to convert to v4.

        Comment


          #5
          RE: Network problems ...

          I don't think it could be the field rules because this works fine on a single machine, just not on the network

          Thanks though ...

          Gary
          Gary S. Traub, Ph.D.

          Comment


            #6
            RE: Network problems ...

            if you defined the lookup on one of the network machines, then the path to the lookup table might be "hard-coded" into the field rule. Redefine the lookup rule, on the server itself if possible. Otherwise bring the whole application onto one of the workstations and redefine the lookup there (making sure that the lookup table is part of the same folder as the rest of the application). Then copy the data dictionary files for that table back to the server.

            Comment


              #7
              RE: Network problems ...

              Peter:

              Thanks for your input. That makes sense - I will try that tomorrow at the office and will let you know the outcome. Thanks again ...

              Gary Traub
              Gary S. Traub, Ph.D.

              Comment


                #8
                RE: Network problems ...

                Actually, I am not sure if that is the problem - all machines on my network have the same directory structure, i.e., path to the application. But, I did redo the lookup and copied the entire application to the server again, and I still get the same problem. However, in the process, it seems that the problem might have to do with the server itself. It seems that when the server is 'dedicated', and not used by anyone, the other stations do not have the problem. Does this make sense, or is there another likely problem?? And if this is the problem, then are users pretty much forced to use the application with a dedicated server?

                Gary
                Gary S. Traub, Ph.D.

                Comment


                  #9
                  RE: Network problems ...

                  Using a dedicated server dramatically improves network speed. (When I go on the server to look at something in one of A5's editors while developing on an adjacent system and there are more than 4 or 5 users the extra resources lost on the server slows them down a bunch.)

                  We've found that if you modify an existing or create a new layout or global script/function on a system that is using shadow the changes are only in that shadow and not made on the server. Since the data resides on the server this wouldn't seem to apply to your problem, but perhaps there is a link between this and your situation?

                  Comment


                    #10
                    RE: Network problems ...

                    Hi Jim:

                    Thanks for your comments. I think I will be going the dedicated server route for my office. However, I would like to resolve this error message so that other users have the choice of not using a dedicated server, and then not getting the error message.

                    Also, I do make frequent changes to layouts, code , tables, etc. on my laptop at home, which I then bring back to the office, hook into the network as a station, and then copy the entire application (all layouts, code, data, etc) to the server. Then, at each station I rerun network optimize, AND then I do a refresh shadow on each station just to be sure everything is copied to the shadow directory of each station. I think this is the correct procedure, isn't it?

                    Is it possible that the particular computer used as server is faulty? Or a network problem external to Alpha 5?

                    Gary Traub
                    Gary S. Traub, Ph.D.

                    Comment


                      #11
                      RE: Network problems ...

                      Gary:

                      I'd go back to Peter's point about explicit paths. While that lookup may not be the specific problem, I would double/triple check that you are not using any absolute drive/path statements in your scripts to open tables or forms and that the database does not have any tables located in external folders.

                      The next thing I would check is the way the drives are mapped and shared. Map the server shared folder as the same drive on all workstations, not as P on one and Q on another. Then check your shortcuts. After observing flaky behavior on certain systems, I discovered that somehow the shortcuts had "flipped" and were pointing Alpha back towards the server for the program files.

                      I always use a complete path such as
                      "c:Program FilesA5V4rtalpha5.exe" "c:program filesa5v4rtshadowosomosom.adb"
                      in the shortcut. The program folder is the "Start In" folder. If icons are used they are copied into the shadow folder and accessed from there and also referred to by explicit path in the shortcut. This adds to the setup burden but, without doubt, reduces the tech support burden.

                      We have dozens of systems on peer-to-peer; operationally it should be identical to a server setup. There are performance differences but, if you have followed the "general guidelines" there should be no code errors on one and not the other.

                      Finian
                      Finian

                      Comment


                        #12
                        RE: Network problems ...

                        We use the server as a workstation in my office. There is no problemwith editing forms and reports on a workstation, trying them out, and then copying them to the server. However if I change field rules I do the editing at the server itself. Otherwise, as I mentioned and Finian has seconded, the path to the server might get placed in the field rule.

                        Comment


                          #13
                          RE: Network problems ...

                          I really do not understand. But, I have now gone back and redefined the path in the lookup field rule again, and I get the same error. Incidentally, the problem is only occurring with lookup tables. For example, if two stations are accessing the same patient, no problem. But if one user is in the patient's form and goes to the referrer lookup table, and then the other user tries to go into that form, it won't work.

                          However, this only happens when using alpha lookup tables. If I use my own, then there is no problem. So the problem is caused by something in the lookup tables on a network. So are you saying that your comments above can fix this. I tried and can't seem to get it to work. I must be missing something.

                          Incidentally, a while ago I mentioned a problem with lookup tables when they are embedded several deep. That problem resulted in me resorting to creating my own lookup tables in a lot of situations. They work well in alot of respects but not as well as alpha's in other respects. I would rather not have to use my own. Is there more I need to learn about lookups, or is this a limitation that others have encountered? And before I embark on changing all alpha lookups to my own, is there something that is just not sinking in? Will version 5 lookups be able to get around these problems.

                          Thanks in advance for any further comments.

                          Gary
                          Gary S. Traub, Ph.D.

                          Comment


                            #14
                            RE: Network problems ...

                            Gary, if the part that's not clear is the path information, I think they're recommending that you use the server, itself, to open Alpha Five and check or re-set the path to the lookup table in the field rule. Don't try to connect to the server from a work station to do this work. If your database is located entirely within one folder you probably shouldn't even include a 'path' in the table field of the lookup rule, just the table name itself. If you have hardcoded a path there, try stripping it out.

                            -- tom

                            Comment


                              #15
                              RE: Network problems ...

                              Thanks Tom. I understand, and I will try that on Monday when I get in the office. By the way, do you use the alpha lookups or do you design your own?

                              Gary
                              Gary S. Traub, Ph.D.

                              Comment

                              Working...
                              X