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

Using Xbasic to change a field's value

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

    Using Xbasic to change a field's value

    Hi,

    I am trying to use Xbasic to change the value of a date field named ENTRDATE and a character field named ENTRTIME.

    The code I am using follows:

    tbl=table.current()
    tbl.change_begin
    tbl.ENTRDATE=date()
    tbl.ENTRTIME=time()
    tbl.change_end(.T.)

    I get an error messages as follows:

    tbl.ENTRDATE subelement is of a different type (ditto for the tbl.ENTRTIME)

    Can anyone explain how to do this? I am sure that it is simple, but I'm stuck.

    Thank you very much,
    Robin Sculthorpe

    #2
    RE: Using Xbasic to change a field's value

    The error message indicates that the field and expression types are different.

    I know you say so, but are you sure that ENTRDATE is a date field and ENTRTIME is a character field? Is the ENTRTIME field large enough to hold a character time value (8).

    Did you once have the fields set as another type? You may need to update the table dictionary to get Alpha to recognize the changes.

    A quick way to check might be to change your code to
    tbl.ENTRDATE=DTOC(date()) and
    tbl.ENTRTIME=val(time()).
    There can be only one.

    Comment


      #3
      RE: Using Xbasic to change a field's value

      Stan,

      Thank you for your response. I am converting an Alpha 4 application to Alpha 5. The ENTRDATE field was a date field in Alpha 4 and when I examined it today in Alpha 5 (by looking at the field rules), it still indicated that it was a date field. I am not at work right now, so I can't double check on the ENTRTIME field, but earlier today I checked and Alpha 5 indicated that it was a character field. Not sure what field type it was in Alpha 4. Wouldn't field types stay the same? At any rate, I will try your suggestions tomorrow. If I need to update the table dictionary, how do I go about doing that? I am just learning Alpha 5, but am a longtime A4 user.

      Best regards,
      Robin Sculthorpe

      Comment


        #4
        RE: Using Xbasic to change a field's value

        Do a "database compact" from the file menu while the control panel is visible. This will update all table dictionaries.

        I modified a script in my setup which contained code similar to yours, but which worked. I changed a statement which stored a numeric variable to a numeric field. I made the statement try to store a character value to the numeric field and Alpha returned exactly the error you report.

        This leads me to believe that, for some reason, Alpha is not recogniqing your field types as valid to store a date and a character string.

        If you find the problem persists after verifying the field types, try creating a new table from scratch with the same field names with the appropriate field types, create the same form and script that you have problems with, and see what happens.
        There can be only one.

        Comment


          #5
          RE: Using Xbasic to change a field's value

          Robin,

          Attachment is a small database with one table and one form.
          Buttons on form will perform your script and modified to enter a new record, with the same field to date() and field to time() assignments.

          I did notice that I had to add a parentform.resynch() to make the change or enter visible as the current record on the form.

          Take a look and see if it's any help.
          There can be only one.

          Comment


            #6
            RE: Using Xbasic to change a field's value

            Stan,

            Again, thank you for all your help. Compacting the database did not help, nor did converting the expressions with DTOC() and val(). Apparently, there is a subtle difference in Alpha 4 and Alpha 5 regarding the field rules for calculated fields. I had set up the fields to be calculated (as opposed to being user entered) in A5 just like in A4 and, apparently, you cannot modify a calculated field. The error message that was generated was not accurate either. I think I had a similar problem previously, so I changed the fields to default expressions which are entered at the start of data entry and skipped over by the user. Now my code works just fine (that is after I added the parentform.resynch() command that you suggested).

            Thank you again so much!
            Robin Sculthorpe

            Comment

            Working...
            X