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

Multi-User 100~300 new records per hour...locking error

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

    #31
    Re: Multi-User 100~300 new records per hour...locking error

    That's fine. These stores are not tied up together in real time, so if you run a query or a report, it will not have the up-to-the minute data. If that's what you want, then that's fine. You could upload the data at end of business day from each workstation and you don't have to ever deal with record locking.
    Last edited by G Gabriel; 08-26-2008, 05:11 PM.

    Comment


      #32
      Re: Multi-User 100~300 new records per hour...locking error

      oops--misread.....
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #33
        Re: Multi-User 100~300 new records per hour...locking error

        while dbf works better when it is character
        For what it is worth, I am one who would disagree. I had many problems with a connecting field as character. I redid it with numeric with 0 problems in dbf.


        .
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


          #34
          Re: Multi-User 100~300 new records per hour...locking error

          Re: converting dbf to sql, try searching the help file for "Export Alpha Five Tables." I think you will find that you do not need any special converter software. I know in testing I have exported dbf tables to mysql.

          Ray

          Comment


            #35
            Re: Multi-User 100~300 new records per hour...locking error

            about key fields as numeric - I have one adb thats running in at least 15 locations for almost 10 years with Alpha where the key fields are all numeric - I have never had any problems. So i see no reason a key and autoincrement field cannot be numeric.

            personally, I think 98.6% of the problem here is when you are assigning the receipt number.

            I know a lot of states will charge you for lost tax when you have missing receipt numbers. But if you assigned the receipt number when the parent record is initially created (in the parent table), and have the receipt number as the linking field to the lineitems, the problems would go away. If they cancel the transaction, then write 'order cancelled' to the record for tax audit purposes.

            I say that because there is another Alpha developer I help once in a while that has an app where they are processing 1,000 orders per day on 50 workstations, and at last count had over 2,000,000 records in one of his tables (which I am trying to convince him to archive.) All 50 stations are using the same tables.

            If you keep it simple and do not do any posting or appending, as to inventory, I think the dbf will work okay. Although I would use a linux server, since there are no opportunistic issues and it is faster than a windows server, and more reliable. Also, since the workstations will be close together, I would use a gigabit (10-1000) lan instead of a 10-100.

            Once a day I would append all of today's records to archive tables. And all of your reports would be made for the archives. That way, your regular tables will always be very small, and much less likely to error. And any inventory updating can be done when you do the end-of-day processing.

            If its a 24/7 operation, still set aside a 2 or 3 minute(tops) time frame where the system is locked and do the processing.
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment


              #36
              Re: Multi-User 100~300 new records per hour...locking error

              Originally posted by martinwcole View Post
              about key fields as numeric - I have one adb thats running in at least 15 locations for almost 10 years with Alpha where the key fields are all numeric - I have never had any problems. So i see no reason a key and autoincrement field cannot be numeric.....
              Just FYI, I agree--I have a major app in which the main key and autoincrement field is numeric and I have never had a problem due to it being numeric. Always found it puzzling why some insist that making such a field a character is superior.

              Ray

              Comment


                #37
                Re: Multi-User 100~300 new records per hour...locking error

                I noticed in all the sample applications provided by A5, the auto-increment fields were character.
                When you guys are creating a new database do you use character or nemeric as your auto-increment as a general rule for dbf?
                Would it be wiser to use numeric if u may one day migrate to SQL?
                How do you deal with the zero-fill?

                Comment


                  #38
                  Re: Multi-User 100~300 new records per hour...locking error

                  Originally posted by mschoi View Post
                  I noticed in all the sample applications provided by A5, the auto-increment fields were character.
                  When you guys are creating a new database do you use character or nemeric as your auto-increment as a general rule for dbf?
                  Would it be wiser to use numeric if u may one day migrate to SQL?
                  As for the latter part, yes I do think a numeric autoincrement field is more useful if you have your eye on migrating to SQL as most SQL databases don't support character autoincrement fields. we usually have a numeric autoinc ID and a unique code/name for customers or products so it's easier for a human being to interpret.

                  Comment


                    #39
                    Re: Multi-User 100~300 new records per hour...locking error

                    Thanks Andrea....

                    Comment


                      #40
                      Re: Multi-User 100~300 new records per hour...locking error

                      When you guys are creating a new database do you use character or nemeric as your auto-increment as a general rule for dbf?
                      Would it be wiser to use numeric if u may one day migrate to SQL?
                      I use numeric on autoinc fields exclusively that are to be used in a set or otherwise. Further, My users never see the set linking autoincrement field. Other fields are mostly character or date, etc. Unless a calculation may be needed or it is in some way essential that it be numeric. If you have a character field size of ten and you start off with one character or number, it is in front and the rest of the field is filled with something. If you start off with a numeric field, the number is on the right and the rest is filled with 0's. It seems more logical to me to be numeric.

                      As far as sql, I have only dabbled, but all my tables are able to make the transition without a bunch of work. Now that the new runtime is out, I am earnestly reworking my apps into v9.




                      .
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                        #41
                        Re: Multi-User 100~300 new records per hour...locking error

                        Originally posted by mschoi View Post
                        I think I got your point. Great analogy.
                        So are you recomending that I use A5 with a MySQL backend(which I have)?
                        I'd recommend this too, converting my DBF apps to mySQL has been rather painless, for both web and desktop bits - I guess the mySQL AlphaDAO drivers are the most tested & least bug free as so many people use mySQL as opposed to Oracle etc.

                        Comment


                          #42
                          Re: Multi-User 100~300 new records per hour...locking error

                          I will switch all my tables to numeric inc.
                          One question.
                          I noticed that in MySQL the first record defaults to "1" while in A5 the first record is "0".
                          Are you guys using the field rules-default mode so that the first record is "1"?
                          So that the SQL record numbers match the dbf?

                          If so, when the very first records that you add to an empty table are appended in I noticed that the fieldrule is ignored and the first record starts with 0 instead of 1.

                          Did any of you notice this?

                          Comment


                            #43
                            Re: Multi-User 100~300 new records per hour...locking error

                            There is a portable version of mysql that's part of the portable xampp package. It works very well, as it's easy to move the server/data from one computer to another. I haven't bother stripping out the php, etc, that I don't really need to create just a true portable mysql, but it works very well.

                            The primary reason I came back to A5 from many years ago, was that now it really has a client/server option. I live in the sql world, Oracle, SQL Server and MYSQL mostly with a little sqlite thrown in, so I am comfortable with it for sure.

                            I have a lot to learn about A5, but I think it is going to be fun. I believe that mysql will work (hopefully) very well for desktop and multiuser apps. A lot of the issues that I hear/see about dbf files, etc, won't be a problem, so we will see how it goes.

                            Alan

                            Comment


                              #44
                              Re: Multi-User 100~300 new records per hour...locking error

                              Since MYSQL has Triggers, you could create your own autoincrementing fields using character fields also.

                              Just a thought, I have not done it, but it should work.
                              I have used the triggers quite a bit, and they work very well.

                              Alan

                              Comment


                                #45
                                Re: Multi-User 100~300 new records per hour...locking error

                                Alan:

                                At present I'm sticking with dbf because i'm scared of the unknown, and I'm in a rush. But as soon as I have the opportunity, I will try migrating to MySQL. I'm interested in knowing how you do with A%+MySQL..
                                I'm a pure A5 guy with no other experience outside of Pascal in college.
                                I got the MySQL free version off the net, and have been playing with it for about a year. A5 doesn't have a blog fieldtype and pictures and image file references were a problem for me to a point (at the time) that I abandoned it.
                                I just finished switching all my tables to numeric auto-increment and also figured out how to have the first record default to 1 (even if appending).
                                As you can see, my tendency is to solve any and all sql problems from within A5. I'm doing this now for the eventuality of going to sql.
                                When it comes to MySQL...what version do you recommend?
                                To be effective do I need to buy the "must-pay" version of MySQL?
                                Also, what applications do you recommend if any? (free is best)

                                Comment

                                Working...
                                X