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

How can I check

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

    How can I check

    I have an import operation that runs by clicking a radio button. How can I check if the operation is run if I attempt to run it again for the day. It should be run once a day only.


    Thanks

    #2
    RE: How can I check

    You could create another table, one field, one record, and use xbasic to write the updated date for your import table. You could also add xbasic to your button to check the date in this field before performing the update, warn the user that the import had already been performed.
    There can be only one.

    Comment


      #3
      RE: How can I check

      One solution might be to create a new table named something like ImportLog. The fields would be named DATE, TIME, USERID and COUNT. Before each import, do a lookup into the ImportLog table using the system date as the key. If no record exists, run the import. If no record exists, display a message indicating that the import has already been run today, and display the date, time, userid and record count of the last import. After each successful import, you could add a record to the ImportLog table. The new record would contain the date, time, userid and number of records that were imported. This is only 1 of many ways to handle this.
      Gary

      Comment


        #4
        RE: How can I check

        Thanks for everybody. I'll start immediately.

        Comment


          #5
          RE: How can I check

          Can you Please tell me what functions to use or how to update afield in a different table when running an import operation.

          Comment


            #6
            RE: How can I check

            updvar = your expression to store if import has been run
            tPointer = table.open("yourtrackingtable")
            tPointer.change_begin()
            fPointer = tPointer,field_get("yourfield name")
            fPointer.value_put(updvar)
            tPointer.change_end(.T.)
            tPointer.close()
            There can be only one.

            Comment


              #7
              RE: How can I check

              I tried the script and I keep getting an error says
              RECORD NUMBER IS PAST END OF TABLE.

              The message is not clear to what's going on .

              Comment


                #8
                RE: How can I check

                If you have no data in your table then you can't "change" anything. I was giving an example of the methods, not a full script. If you want to use this "scenario" and write multiple records you could modify what I posted earlier like:

                updvar = your expression to store if import has been run
                tPointer = table.open("yourtrackingtable")
                tPointer.enter_begin()
                fPointer = tPointer.field_get("yourfield name")
                fPointer.value_put(updvar)
                tPointer.enter_end(.T.)
                tPointer.close()

                The above will write a new record.

                What I had in mind was that you would first have code to read this table

                tPointer = table.open("yourtrackingtable")
                tPointer.fetch_last()
                fPointer = tPointer.field_get("yourfield name")
                when = fPointer.value_get()
                tPointer.close()
                if when = date() then
                display a message saying import has already been done
                end
                end if

                Then you would have a statement here to run your import operation.

                Then you would use the first script I posted:

                updvar = your expression to store if import has been run
                tPointer = table.open("yourtrackingtable")
                tPointer.enter_begin()
                fPointer = tPointer.field_get("yourfield name")
                fPointer.value_put(updvar)
                tPointer.enter_end(.T.)
                tPointer.close()
                end

                If you want only one record indicating the last time the import was run, you would create the table, enter the last import date, then use the "change" version of the script.

                Any clearer?

                Stan

                There can be only one.

                Comment


                  #9
                  RE: How can I check

                  Thanks Stan

                  Actually I was posting a reply while you were doing it the same time. I did add a record and it worked fine.

                  Thanks for all the help

                  Comment

                  Working...
                  X