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

Change in field postion in a DBF-mixed up data

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

    Change in field postion in a DBF-mixed up data

    We use a script to move data from an older version of our application to a newer one. The script is in the new one. The following is the script for one data file. We have about 60 DBF's

    'ACCOUNT
    '-----------------------------
    response = ui_msg_box("Update","Update Account Codes ?",51)
    If response = 6 Then
    filename = DDIR + "\account.dbf"
    result = file.exists(filename)
    IF result = .F. THEN
    answer = ui_msg_box("","ACCOUNT.DBF File does not exist", UI_OK+UI_STOP_SYMBOL)
    ELSE
    a_tbl = table.open( "account.dbf")
    a_tbl.zap( .T. )
    append.t_db = DDIR + "account.dbf"
    append.m_key = ""
    append.t_key = ""
    append.m_filter = ""
    append.t_filter = ""
    append.type = "All"
    append.m_count = 2
    append.m_field1 = "ACCOUNT"
    append.m_exp1 = "@ACCOUNT->ACCOUNT"
    append.m_field2 = "DESCRIPT"
    append.m_exp2 = "@ACCOUNT->DESCRIPT"
    append.t_count = 0
    a_tbl.append()
    a_tbl.close()
    answer = ui_msg_box("","ACCOUNT.DBF Updated", UI_OK)
    END IF
    END IF

    **************************************************

    Both versions have identical structures but the fields are in a different order.

    In old version, account.dbf
    1.account C10
    2.description C20

    In NEW version, account.dbf
    1.description C20
    2.account C10.

    We have noticed that data in larger DBF's appear to be going into the wrong field. Dates going into a character field. On some testing, it looks like both files MUST have the same order of fields.

    Opinions? Or what mite be causing this.

    Thanks.

    DeWayne

    #2
    Suggestions

    I think it's possible the data errors are resulting from errors occurring in your script. Before posting this, I created a simple two table database. The tables had identical fieldnames and datatypes, but the order of the fields was different. Alpha Five had no trouble appending records to the correct fields. The different field sequence in the structure of the transaction table did NOT affect the accuracy of the append. This led me to look more closely at your script.

    Code:
    If response = 6 Then
         filename = DDIR + "\account.dbf"
         result = file.exists(filename)
         IF result = .F. THEN
              answer = ui_msg_box("","ACCOUNT.DBF File does not exist", UI_OK+UI_STOP_SYMBOL)
         ELSE
              a_tbl = table.open( "account.dbf")
              a_tbl.zap( .T. )
              append.t_db = DDIR + "account.dbf"
    You don't show us what "DDIR" contains. However, in line 1 above, you insert a backslash. In the last line above, you do not. One or the other is wrong. Since the backslash is the line continuation character you may need to "escape" it, probably in both places. Check the help file topic "Backslash, using in expressions".

    Next, it's useful to note that your script is not simply appending records. It begins by emptying the master table with the Zap command. Check the help file topic <tbl>.zap(). You will find that to use the Zap method you must open the table for exclusive use, which your script is not doing. When this is fixed you should also consider trapping the error Alpha Five will throw if someone else has the table open.

    Next, you may be assuming the script will pause all by itself while zap is finishing its work. Not true. It will keep running. The result may be that the append actually starts (or tries to) while zap is still working. A better approach would pause the script, using xbasic_wait_for_idle(), before beginning the append.

    HTH

    -- tom

    Comment

    Working...
    X