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

new record - object activate - change begin

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

    new record - object activate - change begin

    I have no idea what the title should be....
    Have been working on this problem (off and on) for about 3 days and going brain dead because I cannot find the solution.

    Here's the 'scenario':
    From a Main Menu - Choose 'transaction' form and open it - the form record order is recno() and edits are disallowed from OnInit event
    From the transaction form - press new record button - this runs a script

    Script:
    Progressive Lookup for customer name - calls a modal form and displays customer data - customer is OK'd (other choices - wrong cus, repeat lookup - cancel new rec - return to transaction form)
    Script fills two vars (vc_cusid1 and vc_cus_lastname) from customer table data.
    Script allows edits and calls new record.
    2 form fields (tx_cus_id and tx_cus_lastname) are filled from the vars

    HERE the problem starts....
    when the script ends, the transaction form is displayed with the two fields properly filled, but nothing done so far activates the first tabstop field (tx date) and allows further data entry. Not even F3...
    At this point, and that may change, I do not wish to change the no-edits when the form is called, and I really don't want to make another identical form just for data entry.

    Code:
    ''open tbl, put in cus data, close tbl, make chngs
    'dim ttx as P
    'dim vn_lastrec as N
    '
    'ttx=table.open("dd_transactions")
    'ttx.enter_begin()
    'ttx.Tx_cus_id=vc_cusid1
    'ttx.Tx_cus_lastname=vc_cus_lastname
    'ttx.enter_end()
    'vn_lastrec=ttx.records_get()
    ''ttx.close() 'this line was not used
    'parentform.Recno_goto(vn_lastrec)
    'this works to here but next 2 lines -- each individually - cause error
    ''parentform.change_begin()
    '':transactions.change_begin()
    In the above code, could not get change to begin - both parentform and :transactions could not be found

    Code:
    object_name = ":transactions"  
    :transactions.allow_change(.t.)	
    :transactions.new_record()	
    :transactions:tx_cus_id.value=vc_cusid1
    ':transactions:tx_Cus_lastname.value=""
    :transactions:tx_Cus_lastname.value=vc_cus_lastname
    ':transactions.refresh()
    ':transactions:tx_appt_date.Activate()
    In above code, transaction form could not be found for the refresh or the activate commands, either together or individually. script errored out and changes could not be made -- again not even with F3

    I really hope this is clear enough --

    Thanx for any help
    D

    #2
    Re: new record - object activate - change begin

    Dick,
    I can't immediately see the issue. I'm wondering in the first code whether you need a topparent.allow_change(.t.) before the parentform.change_begin(). In the second code, I'm wondering if you saved the new record after the two fields were populated and then worked the record in change mode, whether that might work better for you.

    I have an almost exact sequence you described in an Quotes&Invoice database. I put the capability of changing the Client name on the Quote behind a password. This sequence was causing me problems, so I did what I sometimes do. Create the script with Action scripting and see if it works out, and if it does, then backtrack and convert it to Xbasic, and I sometimes get revealed where my problem resided. Good luck..


    Mike W
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment

    Working...
    X