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

Combining live A5 and A4 data, best method?

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

    Combining live A5 and A4 data, best method?

    Hi,

    I have redone my A4 application in A5. Most of the data is in A4, but I have been testing my A5 app. with a small amount of live data. Now I want to move the rest of the A4 data over to the A5 application. I have extensive field rules, memo fields, and some autoincremented fields. I understand that a direct append of live data from A4 to A5 would entail either deleting the data dictionaries or disabling the field rules temporarily and restoring them after the append is complete in order to prevent the field rules from being triggered and the autoincrement fields from being renumbered. (I know that the autoincrement field values in the 2 sets of tables are all unique and do not overlap). However, it would seem simpler to me to create a new folder and copy the A5 data into it (copying the *.dbf and *.fpt files only). Then append the A4 data to the A5 data in the new folder. Then copy the resulting table and memo files to my application, overwriting the old A5 table and memo files. Does anyone see any problems with this method? It seems easier than temporarily deleting the data dictionaries or disabling the field rules.

    Best regards,
    Robin Sculthorpe

    #2
    RE: Combining live A5 and A4 data, best method?

    Assuming the A5 data you refer to is an A5 table that already has field rules in it, appending the A4 data to that table is a good idea, for the obvious reason and one other that you might not have thought of:

    If there is any data in the A4 table that does NOT comply with field rules in the A5 table, Alpha will create a table called VIOLATED.DBF, in which the offending records will be copied, including the reason that they didn't meet the field rules. this is actually a big advantage, because having bad (as in non-complying) data in a table can cause all sorts of headaches.

    Comment


      #3
      RE: Combining live A5 and A4 data, best method?

      I agree with Bill but when you append the data you will still need to remove the auto-increment setting temporarily. That's really not a big deal but you should also make sure you append the highest numbers last. This may mean making a copy of the A5 table, removing all data from the original A5 table, importing the A4 data, then importing the A5 data.

      Cal Locklin
      www.aimsdc.net

      Comment


        #4
        RE: Combining live A5 and A4 data, best method?

        That sort of sounds like what I was going to do, make copies of the tables to do the appends and then copy the resulting tables and memo files over the A5 tables and memo files in the A5 application that I wish to use. I am not worried about any field rule violations as I used all the same field rules in both sets of tables. Thanks for your suggestions.

        Kind regards,
        Robin Sculthorpe

        Comment

        Working...
        X