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

create index for shadow (read only / CD) database

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

    create index for shadow (read only / CD) database

    I have created indexes for shadow databases in Alpha4v6 with no problems.
    In Alpha5v4 the "define index" is greyed out for shadow databases.
    What am I doing wrong?
    Thank you
    Saverio

    #2
    RE: create index for shadow (read only / CD) datab

    Are you using a runtime version or full? runtime doesn't allow this option.
    There can be only one.

    Comment


      #3
      RE: create index for shadow (read only / CD) datab

      the choice of the term "shadow" table in a5 was unfortunate, in that it implies that it is the same concept as "shadow" table was in a4.

      in a5, the term was created to refer to a table that is on the server (or some other remote drive), but whose dictionary is on a local machine. it relates to the Network Optimization feature.

      the key point is that the .dbf and .cdx (indexes) are on one machine and the .ddd .ddm and .ddx (dictionary files) are on another machine.

      a5 does not have the ability to have the production indexes on a different drive/path than the data files.

      the reason that the index feature is greyed out is that the cd rom is read only and so a5 cannot create indexes on cd rom.

      if you refer to the xbasic reference manual on indexes, you will see that in addition to the "production" index (which has the same name as the .dbf file, and is stored on the save drive/path), a5 allows a table to have other indexe files as well. you may be able to use this feature to create an index file (using xbasic) that is stored on the hard drive, while the .dbf remains on the cd rom.

      here is an extract from the xbasic manual:


      .index_create_end()
      Syntax:
      = .index_create_end([Filename])
      Description:
      Creates a new index file for the table referenced by the object pointer, . An object pointer () is returned as a reference to the first tag in the new index file. You can supply an optional Filename (with the .CDX extension). If you do not supply a Filename, the index becomes the table�s production index. It has the same name as the table (with a .CDX extension), and it is opened automatically when the table is opened.
      If you supply the Filename, and it is different than the table name, the index file is not a production index, meaning that you are responsible for opening the index file yourself, using the .index_open() method, when you open the table.
      The .index_create_end() method is used in conjunction with the Table.index_create_begin() and Table.index_add() methods.

      Comment

      Working...
      X