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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Any dll workarounds?

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
    #31
    RE: THANK YOU, THERE IS A GOD!!!

    Hi Bill J. and everyone,

    You wrote :
    "....but unless I'm missing something...any modifications to a table lookup must be made by saving the modification to the table lookup."

    That's right. But you can do it from the lookup screen itself if you enable this option in field rules.

    "...this completely does not meet my needs. The modifications I make to the lookup choices are done on a situational/specific (to that record) basis. In many cases this amounts to a unique entry in that field....If I have to have several thousand choices in the lookup, I may as well just type in each entry from scratch."

    This would be no different with a simple lookup list. It doesn't help to "lookup" unique entries. For such cases, the relevant option is that the entry be allowed even if not present in the lookup source, whether table or list.

    I think there are two distinct issues in this thread.
    -errors due to the length of the entry (the main issue);
    -modifiability of the various forms of lookup source.

    My limited contribution is to the second issue only.

    All the best,
    Bill
    Bill Hanigsberg

    Comment

      #32
      RE: THANK YOU, THERE IS A GOD!!!

      Just for the record, I think what Bill J wants to do makes sense. Just another way to "speed" type by giving the user a lookup list of suggested options. Of course they could just type in anything, but in some cases that might be ok. I just couldn't understand why it wouldn't work. Cal pegged that one. 60 characters or less seems to work everytime. 64 characters or more and boom. My example used 60 characters. Sure looks like a bug to me. A little piece of additional info. I use a crash recovery program called Bomb Shelter which sometimes allows recovery from a crash without closing a program. When I tried to recover, I got a message that system rescources were low. A clue perhaps?

      Jerry

      Comment

        #33
        RE: Any dll workarounds?

        Tom,

        It's interesting that yours seems to crash around 50 characters. My system will work every time at 59 characters but crashes somewhere between 60 and 65.

        It's not necessary to fill the field. Any time the 'magic number' is passed, the program will crash and, in Bill's case, he's saying he needs the extra characters.

        In my case, I made the field only 70 so it wouldn't be longer than the screen but would be long enough to re-create the problem.

        Cal

        Comment

          #34
          RE: Any dll workarounds?

          Cal, when I said that 50 chars wide would not crash and that 70 chars wide did crash, I did not mean to imply that 51 wouldn't work, too. Did not test all the intermediate values since the problem was confirmed.

          -- tom

          Comment

            #35
            RE: THANK YOU, THERE IS A GOD!!!

            Hi Guys,

            I haven't invetigated this, but I'll bet you donuts to dollars, that the problem is that the index key is effectively limited to something in the order of 50 characters.

            Unfortunately, if you were to put a truncate the index value to 50 characters, the lookup field rule would automatically create another index without the left(fieldname,50). The solution is to limit the field size. As to the exact number, that's just a function of the exact system configuration of the PC, and might vary a bit.

            Part of this may be due to the index integrity checking now added in version 4.5

            Regards,

            Ira J. Perlow
            Computer Systems Design & Associates
            [email protected]
            Regards,

            Ira J. Perlow
            Computer Systems Design


            CSDA A5 Products
            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
            CSDA Barcode Functions
            CSDA Code Utility
            CSDA Screen Capture

            Comment

              #36
              RE: THANK YOU, THERE IS A GOD!!!

              Ira,
              I used V4.03 build 230 and could generate the crash. Also, I can find no index being generated. Having said that, I suspect you are on the right track. I suspect there must be some restriction on the resultant filed length in the Alpha code somewhere. An interesting side light is that I can create a lookup value of 70 characters and can do a lookup and use that value without a crash. But add 1 character to the field and a crash occurs.

              Actually, I would prefer the dollars to donuts. I hope someone at Alpha follows this thread and gives a solution or an explanation.

              Jerry

              Comment

                #37
                WOW finding bugs is kinda fun, killing 'em...?

                Hi all,
                I tried and got the same results, make a lookup choice that is any length (up to the defined length of field)and no problem, but try to add one more character after the fact and...see ya. Not only that, but I've gotten lockups that force me to cut power to the computer, not even the on/off button would function. This is SCARING the #$%* out of me. I decided to look at a table lookup again to see if it would meet my needs and Bill H. was right, it can be done but... any lookup choice can be modified without crashing (so far) but I find I have to use my backspace or delete key, to create space in the field so it can be added to. Example; field length defined as 240, chosen entry is "busy signal times" [17 characters]. In order for me to be able to add, say the number 3, to that entry, I have to place the cursor past the entry and delete characters beyond it or backspace to it, to create space. Is there any way to do this where the cursor would be placed at the end of the entry[once the choice is made], in the ready to enter mode?
                This may seem trivial to some who are following this thread, but it's something I've gotten used to being able to do, and something that makes sense to me, in terms of automating tasks and minimizing data entry. Which is, after all, what a good database program is all about.
                Just as importantly, it's the reason I hesitate when upgrades become available. I can't remember the details, but I've lost some features/functions that I grew to like, every time I've upgraded.

                Comment

                Previous 1 2 3 template Next
                Working...
                X