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

Is there?

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

    Is there?

    Is there a function that will comapare 2 tables that will check for "fieldmame", "field type", "length" and decimal "places" ? I've looked all over for such a function without results.

    I'll be very grateful for any and all replies,
    efs

    #2
    RE: Is there?

    Ed, I don't understand your question.

    Are you trying to determine if two tables have the same structure? May I ask why ?

    -- tom

    Comment


      #3
      RE: Is there?

      Edward

      It is possible using xbasic to get all of the field names for a table. The sections in the xbasic manual on table methods show some examples. The section on tbl.fields_get() shows how to get a list of fields. Once you have a list of fields, you can use functions like fld.name_get(), fld.type_get() fld.dec_get(), and fld.width_get() to get all of the structure information.

      But as Tom points out, why? I have one case where I do save index structure information gathered by xbasic, but I can't see any reason to get table information. Actually, if you just need to record the information, check out the A5doc program. It will give you all of the structure information in a report or saved in a table.

      Jerry

      Comment


        #4
        RE: Is there?

        Hi Tom & Jerry,

        The reason I need this is because I have 8 append operations where 2 of them provide errors, the error leads me to believe that some of the fields do not match. In 1 case I found a field supposedly named client_nam, that appeared in the table structure as client_na (no N on the end. The weird part is that the second set of tables had been copied from 1 machine to the other using a burner.

        Thank you both for responding,
        Ed

        Comment


          #5
          RE: Is there?

          Edward

          You say one set of tables was copied using a burner. A file placed a CD is set readonly. When the file is copied to a drive, that attibute has to be turned off manually. If is isn't you can't open the file for any edit.

          Another problem is long file names. What you are seeing may be name truncation where the long name is lost. If ANY of the field names are more than 10 character, this can occur. The long name definition is saved in the table data dictionary files (ddd, ddm, ddx). If these are missing, or can't be opened (readonly), the long name is lost and you will see either 9 or 10 character names only.

          Jerry

          Jerry

          Comment


            #6
            RE: Is there?

            Jerry

            That is a great and informative reply, Jerry. I have been aware for sometime about the read only attributes that a CD puts on the files, I had already taken care of that part. But this is the best explanation of field names over 10 characters, that could be my problem. I had already found 1 field that was missing the last letter, I am sure that is where the problem lies. Thanks a bunch.
            Ed

            Comment


              #7
              RE: Is there?

              Ed

              The problem with truncated field names is that it can be erratic and not always occur. One situation where is seems to be an issue is if the tables are zipped up in a compressed file and then unzipped. For some reason, this on rare occations caused problems for me until I quit using any long names.

              Because of the way Alpha generates the short name from the long name, the first 9 characters should never be the same for 2 fields if long names are used. Alpha takes the first 9 charactrers and adds a numeric character to generate the short name. If 2 fields have the same first 9 characters, this can cause a problem.

              The short name issue is really not an Alpha problem as such but a situation forced by the use of the dbf format that doesn't natively accept long names. I just stay totally away from more than 10 characters in field names or index names (they have the same limitation). For the same reasons, avoid spaces and any punctuation other than the underline.

              Jerry

              Comment


                #8
                RE: Is there?

                Jerry,

                Thank you very much for your tip. I was able to prove you were right on the money about 10 characters in a field name. I have 2 tables that were affected, 1 of them was a minor problem I could change the field name without it worming it's way into scripts and indexes, the second table remains a problem since the long fields are involved in scripts and indexes throughout the application. Which leads me to the dictionary files, can I email those as well and hence preserve the long names?

                I learned a big lesson,
                Ed

                Comment


                  #9
                  RE: Is there?

                  It appears that even a 10 character fieldname might be touchy also, since it truncated the "n" off of client_nam.
                  Ed

                  Comment


                    #10
                    RE: Is there?

                    Ed

                    There was an article in the newsletter some time ago about file structures that talks about this. If you use long names in a field or index, you have to keep the data dictionary files with the dbf and cdx files. They are now linked, since some of the information about the names is saved there. Once you have experienced this type of problem, the idea about using long names is quickly put in the trash heap for most projects.

                    Jerry

                    Comment


                      #11
                      RE: Is there?

                      Ed,

                      You might want to take a look at my little "treatise" on naming conventions on my Tips page at www.aimsdc.net/Tips.htm.

                      Comment

                      Working...
                      X