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

Illegal operation when cutting a record

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

    Illegal operation when cutting a record

    In one table, every time I cut a record, I get the error message about the Illegal Operation, and then the program crashes.

    I've done all the obvious: pack, rebuild indexes, re-add the table, change a memo field to a character field - all to no avail.

    Any ideas, anyone?

    Thanks,
    Wanda

    #2
    RE: Illegal operation when cutting a record

    Having never attempted to cut a record, I'm curious how you do it, and why?

    If you are trying to delete a record or to just copy it to the Windows clipboard there are 'better' ways to do it.

    -- tom

    Comment


      #3
      RE: Illegal operation when cutting a record

      Wanda:
      I think you want to delete or mark a record.
      deletion is permanent with in normal context of A%
      Marking the record leaves it available to normal use unless your logic selects or deselects marked records.

      bob

      Comment


        #4
        RE: Illegal operation when cutting a record

        Thank you for answering my post.

        I had just gotten used to cutting, rather than deleting...("cutting" is using the scissors). I just entered a dummy record and "deleted" it, and the table crashed again, shutting the program down.

        Curiously, there is a report designed with a set which includes this particular table...and it won't print, anymore. I've never had the problem of it not printing, but I have had the problem of it crashing, which used to happen randomly. Now it happens every time I cut or delete.

        Any other ideas?
        Sincerely,
        Wanda

        Comment


          #5
          RE: Illegal operation when cutting a record

          I just wanted to add that the first of 63 pages printed (indicating, as well that it was page 1 of 63).

          Comment


            #6
            RE: Illegal operation when cutting a record

            Have you tried compacting the database file?

            -- tom

            Comment


              #7
              RE: Illegal operation when cutting a record

              Yes, I have, and all the other normal stuff one does...here's a breakthrough, though. Prior to the report not wanting to print I added a character field that I had converted from a memo field. Just now I deleted the field from the report and it prints. I also had added a dotted line in the detail section...so the printing problem seems to be linked to those pesky memo fields!

              I believe if I get rid of that field all together - and never again use memo fields (until the bugs are ironed out), that the report will work just fine...I'll post my progress.

              Thanks again,
              Wanda

              Comment


                #8
                RE: Illegal operation when cutting a record

                Yup - that was the problem. I created another field, manually entered the data that was in the character field which I had changed from a memo field (thankfully there wasn't that much in the field, so it didn't take all that long) - then I deleted the field which had preveiously been a memo field - and the report prints just fine now.

                There's one slight oddity I will mention, even though I can get around it: when selecting a field to place on the report layout, I get an error message telling me there's NO SUCH TABLE. Hog wash, I say! To get around this, I copy another field, then go into Report Properties and select the real field that I wanted in the first place. It works.

                Thanks to everyone for their ideas.
                Wanda

                Comment

                Working...
                X