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

Problems with .active, any suggestions Please?

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

    Problems with .active, any suggestions Please?

    trying to edit the "active" field on my browse. where am I going wrong?

    thx

    Code is as follows:

    Code:
    on error goto error_routine
    active_field = topparent.active(.f.)
    t = table.current()
    t.fetch_first()
    while .not. t.fetch_eof()
    t.change_begin()
    eval("t."-active_field) = No_Diacritics(eval("t."-active_field))
    eval("t."-active_field) = Repl_strings(eval("t."-active_field))
    t.change_end(.t.)
    t.fetch_next()
    end while
    end
    Code:
    FUNCTION no_diacritics AS C (input_string as C)
    no_diacritics=CHRTRAN(Input_String,"ÊÈéáãæâêéàî˜óñËÛÏšñŽñÕËüçôäúèÉëÉ","EEeaaaaeeaionEUIsnZnOEucoaueEeE")
    END FUNCTION
    Code:
    FUNCTION repl_strings as C (input_string as C)
    find_strings = <<%find%
    ã
    é
    °
    %find%
    repl_strings = <<%repl%
    a
    e
    -
    %repl%
    repl_strings = stritran_multi(input_string,find_strings,repl_strings)
    END FUNCTION
    Code:
    error_routine:
    err_msg = error_text_get(error_code_get())
    script = error_script_get()
    line = error_line_number_get()
    ui_msg_box("Error",err_msg+" error occured at line "+alltrim(str(line,4,0))+" in Script "+alltrim(script))
    end​
    I keep getting error message
    Command does not work in change or Enter Mode
    Error occured at Line 8
    --
    Support your local Search and Rescue Unit, Get Lost!

    www.westrowops.co.uk

    #2
    Graham,

    I’m a very simple person. You have to understand that you are intimately familiar with your code and what you are trying to do. I’m looking at your code and I’m trying to understand what you are doing. Again, I’m a very simple person.

    I recommend that you turn on line numbers in your code. It would make it easier for me any anyone else trying to help you.

    I also recommend the use of the “debug(1)” function allowing one to step through the code one line at a time.

    Lastly, I would recommend building a very simple table and browse to test on. All you would need is a table with enough records to test your functions and a single column. What usually happens with me, when I build a simple example to submit to the message board, I usually find the error.


    That said, it appears to me that the line throwing an error is:
    Code:
    eval("t."-active_field) = Repl_strings(eval("t."-active_field))
    Your error message is sayi
    ng because the table is in change mode, something in the function you called can not run.

    I would change your code to:

    Code:
    on error goto error_routine
    debug(1)
    I would put debug(1) in each function if needed.​
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    Comment


      #3
      Remember to remove/comment out any debug(1) statements once you've finished with them or the runtime will halt each time one is reached. This is very painful in V12 as the debug windows doesn't show up in the runtime.

      Comment


        #4
        Graham,

        For the benefit of others on the message board, did you resolve this issue?
        Alpha 5 Version 11
        AA Build 2999, Build 4269, Current Build
        DBF's and MySql
        Desktop, Web on the Desktop and WEB

        Ron Anusiewicz

        Comment

        Working...
        X