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

Primary Index changing after File.copy

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

    Primary Index changing after File.copy

    I have been using the File.copy function to copy a .dbf file from a network database to the one on my computer. Thus, copy database1 and save it as database2. I had a primary index selected for database2, but for some reason it changes to record number order (the default) after the File.copy function occurs. Is this typical of A5? and if so, should I use an append operation instead?

    I really would like to keep the primary index the same, but to transfer at a faster rate than the append.

    #2
    RE: Primary Index changing after File.copy

    Nathan:

    If you go to pages 214 and 215 of the XBasic reference manual, there are two commands that may help. They are the .index_primary_get() and the .index_primary_put() commands.

    I have not experimented with these in relation to your problem, but you should be able to reference any specific index within a script.

    I'm not sure if the table remains on the same index if you open the table in a later session, though. If you test this out, please let me know.

    Perhaps others have some thoughts here.

    By the way, did you go over to ZDNET and leave a review of Alpha Five yet? I recognize your name, so I know your an avid user!

    Craig

    Comment


      #3
      RE: Primary Index changing after File.copy

      "file>.copy()
      Syntax:
      "File>.copy( Destination Filename)
      Description:
      Copies a file, referenced by the object pointer to the Destination
      Filename. If you copy files between specific drives and directories, include the
      full drive and path with each filename.
      You can use this method to duplicate any type of file, including tables, sets, and
      applications. However, to copy a table, set, or application you must remember to
      copy all related support files.
      For a table this can be up to six files: the table
      itself (.DBF), the memo file (.FPT), the index file (.CDX), and, if present, the
      three files that make up the data dictionary (.DDD, .DDM, .DDX). When
      copying tables it is easier to use the "tbl".duplicate() method instead, since
      duplicating a table automatically duplicates all support files and data
      dictionaries.
      There can be only one.

      Comment

      Working...
      X