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

upgrade problems

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

    #16
    RE: upgrade problems

    Hello Al:

    Good job! There is one constant we can usually count on with Alpha Five, there is almost always more than one solution for the same problem.

    And yes, I'm surprised the update worked with AutoIncrement active.

    Robert T.

    Comment


      #17
      RE: upgrade problems

      Robert

      You solved it without seeing it. I had Mary email me a copy of the database. Made it a lot easier to do.

      As far as the auto increment and the update being allowed, it takes an abnormal sequence for it to occur. Normally the operation comes back and says zero records updated. But in design mode and pressing the run icon 2 or 3 times, it will change the data in the auto increment field.

      Strange, but could be Ripley Believe It or Not material.

      I'll sent it to Selwyn.
      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


        #18
        RE: upgrade problems

        Hello Al and Mary:

        Once you get your auto increment working, there are two other issues that must be addressed.

        [1] If the highest number in the current table is 0000004675, you don't want the next number showing up as 4676, obviously you want 0000004676. I believe the autoincrement rule will take care of that for you. If not, there are ways to force [pad] zeros.

        [2] We did not talk about the issue of linking fields in sets. If you have parent or child fields linked to this table we just updated, you lost your links. You will have to run the same operation we ran earlier on this table [with the autoincrement field rule] on those tables that are linked in one to many sets.

        Why? Because 4675 will is not a link with 0000004675. The numbers in both the parent and child must have all the zeros padded.

        Robert T.

        Comment


          #19
          RE: upgrade problems

          Hi Al & Robert,

          SUCCESS! Al very kindly emailed me an expression for updating the fields ... and Robert posted another one here.

          I tried both ... and both worked ... except ... that initially, while Al's permitted me to continue on without having zero place holders, when I went to isolate a given "order" for printing, I couldn't "find" with that number ... it looked instead for the recno.

          That would have been fine for me ... but not for the person who generally does the input.

          Our database is slightly different in that not all orders are "new" orders. We have lots of "repeat" orders wherein the only thing we do is change the "due date" and the item details ... so it's necessary sometimes to isolate a given order for printing.

          I played with Rob's expression, which was great for replacing the spaces with zeros ... but, naturally THAT wasn't good enough for me ... I wanted leading letters ... like "TTS-" and "Customer_#" etc and Rob's expression didn't permit that. However, when I tried this formulation with Al's expression, it worked ... beautifully!

          And thanks for the "child database" reminder Rob. I did update all the appropriate fields in the appropriate sub-databases.

          For the benefit of anyone else who is having this problem, the expression I used was the "padl" expression.

          padl((alltrim(fieldname)),#spaces,"desired_prefix")

          Thanks for all the help! I'd never have figured this out myself!

          Mary E. Lea-Bannister

          Comment

          Working...
          X