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

trace window

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

  • trace window

    how does the trace window work? how do you tarce an event? i have an import that will not work because of invalid field name. There are close to 100 fields. I am sure the trace window can tell me which one is invalid, I just can't figure out how to trac an event.

    Thanks,
    Alan

  • #2
    RE: trace window

    I think the message you are getting is bogus. I also need to import a file with more than 100 fields and I get the same error. I suspc the reason is "too many fields", rather than an invalid field name.

    I'm going to try Alpha 6 and see if the same problem happens as I need to get this info imported ASAP.

    Comment


    • #3
      RE: trace window

      The trace window is accessible from the 'View' menu. It will show you some types of errors that have occurred. If you want to manually write to it, you can use the function trace.writeln().
      Aaron Brown
      Alpha Software Development Team

      Comment


      • #4
        RE: trace window

        Alan

        I've normally been able to find problems with imports by opening them in design mode and using the down arrow key to move through row by row of field names.

        It'll stop on a row with a problem.
        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.

        Comment


        • #5
          RE: trace window

          Open your database; go to control panel.

          choose View from top menu
          Choose Trace window.
          Check the box that says "Trace events"

          Fieldnames must meet DBF format standards.

          If your source is an EXCEL file, try exporting to a DBF file first. You should be able to Append the new DBF.

          -- t

          Comment


          • #6
            RE: trace window

            Dale, the DBF format used by both v5 and v6 allows for 1,023 fields in your table. Unless you have more than that, the error about an invalid field name is probably accurate.

            -Lenny

            Lenny Forziati
            Vice President, Internet Products and Technical Services
            Alpha Software Corporation

            Comment


            • #7
              RE: trace window

              I've done that - moved through all fields in design mode and I encounter no errors - this is very frustrating as Alpha won't tell which field name is the problem...

              Comment


              • #8
                RE: trace window

                The down arrow method didn't work. What did work was setting the "import" option to No and then going through and changing a group of fields at a time to "yes" then testing the import. That enabled me to narrow things down to the one bugger.

                The .csv files I was given came from a system with little to no data integrety rules, unfortunately. I definately need Alpha's operation capabilities to whip the data into shape for final processing. Trying to do this in another DB product leaves me with chills... ;-)

                Thanks for the lead - some of my sanity has been restored...

                Comment

                Working...
                X