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

Spin Control for Date field - Help!

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

  • CALocklin
    replied
    RE: Spin Control for Date field - Help!

    Also take a look at the .resynch() command and the .refresh() command under Xbasic Methods for Working with Forms and Browses.

    Leave a comment:


  • Tom Cone Jr
    replied
    RE: Spin Control for Date field - Help!

    Spend some time in ch. 12 of the xbasic Ref. Manual. You'll find the parentform.mode_get() command explained.

    -- tom

    Leave a comment:


  • Rob Schippers
    Guest replied
    RE: Spin Control for Date field - Help!

    Thank you for that.

    It worked fine, then I put my card_resynch() back in, which was there to update another field on the form, then it stopped working again!

    So the problem was the resynch itself.

    Now I just need to find another way to update the secondary field - that should be easy enough.

    I have yet to find how to determine if the form is in data-entry mode, so I can make the code different for that.

    Leave a comment:


  • Tom Cone Jr
    replied
    RE: Spin Control for Date field - Help!

    Here's an example, showing one way to implement this kind of thing in Version 4. I've tried to heavily comment the scripts, but don't hesitate to ask questions if something isn't clear.

    Unzip the attachment to a separate folder. Do not mix with your development work

    -- tom

    Leave a comment:


  • Rob Schippers
    Guest replied
    RE: Spin Control for Date field - Help!


    My buttons look something like this:


    [ field ][^][v]



    (Two small square buttons next to the field with ^ and v text in them to show up and down.)

    The script to edit the field is in the buttons

    Leave a comment:


  • Tom Cone Jr
    replied
    RE: Spin Control for Date field - Help!

    The books by Dr. Wayne, available from Alpha Software, are good places to start.

    The Xbasic Reference Manual is a useful resource, but it's more of a reference book than a tutorial or teaching aid.

    What's an 'up and down' button ?

    -- tom

    Leave a comment:


  • Rob Schippers
    Guest started a topic Spin Control for Date field - Help!

    Spin Control for Date field - Help!


    Anyone know how to do this in A5 4.5 - I'm just starting to convert from A5 V1.

    I used to have a date field in A5 v1 where I had placed an up and down button next to it with code in it as follows:

    if db_mode_get(db_current())=0 then
    end
    end if
    if isblank("timesht2->date")then
    timesht2->date = previous("timesht2->date")+1
    else
    timesht2->date = TIMESHT2->DATE+1
    end if
    card_resynch()

    This worked in both change and enter modes.


    Having converted this form to A5 v4.5 this did not work any more. If I hit my button in view mode, nothing happened. If I hit it while entering a new record, it popped me back to an existing record. I got it to work in view mode - which is now the same as change mode??? by editing it as follows.

    if isblank("timesht2->date")then

    :data_entry:tables:timesht2.change_begin(honor_field_rules)
    :data_entry:tables:timesht2.date = previous("timesht2->date")+1
    :data_entry:tables:timesht2.change_end()

    else
    :data_entry:tables:timesht2.change_begin(honor_field_rules)
    :data_entry:tables:timesht2.date = data_entry:tables:timesht2.date + 1
    :data_entry:tables:timesht2.change_end()
    end if

    card_resynch()

    But I have not succeeded to get it to work in enter mode. This obviously requires different code??




    I tried the built-in smart-field spin control also. Whole new adventure!!!

    First I tried pasting the sample code into the forms init event. This code would dissappear every time i closed the window.

    I finally added a command to the init event, this made it go black. Then I converted the command to x-basic, then edited the code, then replaced it with the spin-control code, then it worked.

    Except it increments only the day number in the date field and not the entire date.





    Where does one find info to get started with the new code editor, and how to modify the content of fields with xbasic?? for example I searched for change_begin in help, and it did not even show up??

    I think I need to know how to determine in code if the form is in edit or enter mode??
Working...
X