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

Using an underline in table name--post problem

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

    Using an underline in table name--post problem

    Here is a new one (I think). Is the use of an "_" (underline) not permitted in a table name? I've use underlines for years, but today, as I am trying a new operation (a posting of records) it is messing up. I am pretty sure that it is the underline that is the culprit because of the following:
    The name of my "main" table is Name_Etc.dbf. I created and have tried to run a one field, very simple, posting operation from one table to this one. Each time I ran the post, the program froze. Same time, same place. I tried it on 4 different machines before embarking on a debugging operation, and got the same results on each one. I could exit only via Ctrl-Alt-Del.

    So, I duplicated the database (a complete duplication, including data, field rules and disctionary) to NameEtc.dbf (no underline), and ran the same operation (the one that wouldn't run before). It worked perfectly.

    Lest you conclude that the duplication corrected an error in the duplication process (and therefore it wasn't the name difference at all), here's the kicker: I deleted Name_Etc.dbf from the disk (to get rid of all traces) , and then duplicated NameEtc.dbf to Name_Etc.dbf. The subject operation wouldn't run, and the program froze (just like the first attempts.) Same time, same place. 2 different machines.

    I can send the data if A4 tech want a shot at it.

    Roy

    #2
    RE: Using an underline in table name--post problem

    about half of our tables haf an underline in the name, and we use post, update, and append ops on most of them. Just finished doing multiple updates and posts on 4 of them to convert a client. No problems (other than it taking all weekend - lots of stuff had to be done).

    Is there a possibility you have an index / filtered index problem?

    Are you running the post from an operation or in xbasic? I've had some funny stuff happen with a couple 8 hour posts (when we do it, we do it) as operations which were fixed when run in xbasic.

    Comment


      #3
      RE: Using an underline in table name--post problem

      In reverse order:

      I tried the post from both an operation and an xbasic script. Same results as I have related above. With both tables. (i.e., it didn't work with name_etc, it worked with nameetc, and it didn't work when I duplicated nameetc back to name_etc.)

      I have rebuilt the indexes several times. The common field (and therefore I presume the index) used for the post is simply the donors number (one field, seven characters).

      It has become very frustrating, as you might imagine.

      Roy

      Comment


        #4
        RE: Using an underline in table name--post problem

        If it's not corrupted and works when the name changes, the only other thing I can think of is that name_etc might be some form of internal variable. I think that Alpha's variables start with a_ or _a, but who knows about the overall engine?

        If it works one way and not the other, I think I'd consider using the name that does work and make whatever modifications that requires elsewhere (other tables' field rules, set, etc). It's a pain, but I can't think of anything else.

        Comment

        Working...
        X