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

Copy Open Dbf

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

    Copy Open Dbf

    I've looked around through the forum, but surprisingly I could not find an instance of someone having this problem. I have a networked app where people are constantly putting things into one particular dbf. Every 15 minutes or so I want a copy operation to run taking just the daily records from today and copying them to another database. Easy to do? Well, I keep getting an error on the copy operation saying that "the process cannot access the file, because it is being used by another process" which to me means that the dbf is open. I'm not sure why the copy process needs exclusive access and I haven't tried coding it outside of the operation code, but why is this so and secondly is there some sort of workaround anyone has thought of?

    Many thanks!

    Charlie

    #2
    Re: Copy Open Dbf

    Try this as the field rule onsaverecord event code for the table you are copying from.


    Code:
    dim tbl_source as P
    tbl_source = table.current()
    on error goto failed_to_copy
    result = tbl_source.copy_record_to("tabletocopyto")
    on error goto 0
    end
    
    failed_to_copy:
        ui_msg_box("Record not copied.", error_text_get(error_code_get()))
    end
    Your current table and the table you are currenty appending to should always be in sync.
    There can be only one.

    Comment


      #3
      Re: Copy Open Dbf

      Stan, this may be more complicated. Won't your approach create new records in the external table each time a change is made to an existing record? Charlie hasn't given us many details. It's not clear how he handles edits to existing records. Presumably the copy op would create multiple records in the receiving table, though I'm not sure.

      Charlie, it's odd to me that you're using a copy operation instead of an append. Are you creating separately named tables every 15 minutes?

      -- tom

      Comment


        #4
        Re: Copy Open Dbf

        Won't your approach create new records in the external table each time a change is made to an existing record?
        Yep. Didn't think of that.
        There can be only one.

        Comment


          #5
          Re: Copy Open Dbf

          Maybe use the result of the suggested code to add records to an intermediary table from which one would append unique, replace existing to the final table?
          There can be only one.

          Comment


            #6
            Re: Copy Open Dbf

            Thanks guys! With all the coding I am doing it was just odd to run into this. As way of more information, the reason I am copying the selected information was to save time and speed up input. The copied info was placed from dbf1into dbf2 and then dbf2 was FTP'd to my VPS server. Actually I was only copying from dbf1 the records for that particular day. This helps out on the network strain and also on the size of the transmitted FTP file. And, if the FTP transfer fails, it doesn't create problems for dbf1.

            But, why does the copy operation need exclusive access? Would an export operation require exclusive access?

            I'll try the different solutions and let you know.

            Thanks as always. You guys are the best!

            Charlie

            Comment

            Working...
            X