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

ISBN Fields

  • Filter
  • Time
  • Show
Clear All
new posts

  • ISBN Fields

    I'm writing a database that is basically a library operation. I was just wondering how you that have done this are handling the ISBN field? Or are you breaking it up into the 4 specific fields? Are you hyphenating within the field?

    I looked in the forum 'search' and found nothing except one with no response. I may also need to poll a website to lookup and ISBN and return title, author, etc.

    Interesting project---!

  • #2
    RE: ISBN Fields

    If you need to search or index on parts of the ISBN, it would be better to store the parts in separate fields and concatenate them when the full ISBN is needed in reports, forms, labels, etc. If you never need the parts of the ISBN individually, then store it in a single field. In general, it's easier to store parts and put them together when needed than it is to store a large string and take it apart when the parts are needed.


    • #3
      RE: ISBN Fields

      You could set a mask in the field rules so that the operator does not neet to deal with the dashes.


      • #4
        RE: ISBN Fields

        I would do that but sorting might be a problem since it would then no longer be a numeric field.


        • #5
          RE: ISBN Fields

          Don't use a numeric field unless you're going to do arithmetic operations on the data. Use a character field. If you need to sort numerically, you can use the expression val(character field).


          • #6
            RE: ISBN Fields

            I'm thinking you might be right--except that a string like 1-254-2343-1 when taken with the val function will not return the complete numeric value of 125423431 I don't think. I could always break the number into 1 254 2343 1 in four seprate fields (which is the ISBN format) and then sort (if I wanted) by the second field then use the str$ function to create 125423431 from str(1)+str(254)+str(2343)+str(1). I'd be tending toward this method at this point but I can see your suggestion too. I might be waxing a bit philosophical here. If ISBN had even one alphanumeric character in its string--that'd cinch it. But all numeric I'm tempted to go with numeric fields. I wonder what the big boys and girls do?


            • #7
              RE: ISBN Fields

              I see your problem. In general, use numeric fields only when you have to do a numerical operation. The difficulty is in numeric fields:


              In character fields:


              And it's always possible I don't fully understand the problem and I know I don't understand the ISBN system.


              • #8
                RE: ISBN Fields

                Well, I found another reason. ISBN fields last number is a check sum. So I do have to do calculations if I want to do that. Thanks everybody for your time.