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

V5 beta FoxPro CDXs

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

  • V5 beta FoxPro CDXs

    How do I use the production cdx (the one with the same name as the FoxPro table) in V5 beta. I am adding the table to V5 beta in the following manner:

    Control Panel
    Table/Sets TAB
    File
    Add Table/Set
    (Selct the dbf that you want)
    Add Table
    OK

    The table Icon appears in the work area but I can find no way to bring the production cdx into Alpha5 so the cdx will be updated by Alpha5 and the tags can be used for queries and so on.

    Thank you in advance.

    djl

  • #2
    RE: V5 beta FoxPro CDXs

    i presume you are talking about foxpro v2.6 table because these are the ones that a5 uses as its native file format.

    a5 automatically associates the production .cdx file with the table when you open it. the assumption, of course, is that the production .cdx file has the same name as the table.

    so, if your table is called customer.dbf, then the assumption is that the indexes are stored in customer.cdx.

    if that is NOT the case, and you have an index file that has a different filename, then you can still have a5 open and maintain the indexes in that file, however, you will have to use xbasic code to open the .cdx file each time the table is opened. while a5 supports this, it would be extremely rare to have an index file with a different name than the table it is associated with. i have never heard of an a5 user doing this.

    Comment


    • #3
      RE: V5 beta FoxPro CDXs

      Selwyn:

      You are correct in the the cdx is the same name as the dbf.
      However when I add the table to a5 as I described (remember that I am using a5 v5.0 beta) I don't see anywhere I have access to any of the indexes.

      What am I missing here?

      djl

      Comment


      • #4
        RE: V5 beta FoxPro CDXs

        Have you checked the folder to see if the .csx files are there?

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment


        • #5
          RE: V5 beta FoxPro CDXs

          Dave,

          If your CDX is Foxpro 2.6 compatible,

          Select Tables / Sets tab in the Alpha Five control panel;
          Right click on desired table;
          Define or update indexes is an option on the drop down list.

          Also, if you open the default form for the table, and press Ctrl-I, you'll get a little dialog box that lets you select among various indexes.

          -- tom

          Comment


          • #6
            RE: V5 beta FoxPro CDXs

            I have done these things...

            I have never seen any of the indexes in the production cdx.
            Do I have to go into the "define index" area and redefine all the indexes that are already in the cdx so that A5 can use them? I would have thought that one I select the table to add the system would automatically bring in the production cdx.

            djl

            Comment


            • #7
              RE: V5 beta FoxPro CDXs

              No.
              I just opened Alpha5 v5 beta, added my table from the control pannel, created a default form, default browse, saveded them and tried to create a little query to search by last anme. There is a lastname index in the cdx but I couldn't find how to access it anywhere. ^I does not bring it up...

              djl

              Comment


              • #8
                RE: V5 beta FoxPro CDXs

                you didn't answer which version of foxpro created the indexes. you shouldn't have to re-create the index if the index is a5-compatible.
                you also have to make sure that the .cdx file is in the same folder as the .dbf file.

                Comment


                • #9
                  RE: V5 beta FoxPro CDXs

                  FoxPro v2.6 DOS creeated the cdx. FoxPro v.2.6 maintains this cdx just fine. We have bothe DOS progrgams and Windows programs accessing the sames files at the same time, no problem.

                  Because I have been told that A5 uses FoxPro v.2.6 files as it's native format, I should have no problem.

                  I may have done something wrong when I added the table to the v.5.0 beta control panel. I tried to start over again by removing the table from the system and adding it again. I must have to do something else also because a couple of indexex/queries that I had created before are still in the system when I press ^I.

                  I am going to try an entirely differt table that has a production index and see how that goes...

                  Thanks everyone for all your help.

                  djl

                  Comment


                  • #10
                    RE: V5 beta FoxPro CDXs

                    Well...

                    That's the problem!

                    I must have done something wrong when I first added the table. When I added another table with a cdx. every one of the indexes are avail. when I ^I.

                    I need to be able to completly remove the first table from the system and start over. When I try to do this with the "remove table" button or menu option, it dissapears but the index/query stuff is stall laying around somewhere! I need to know how to get rid of that also and start fresh!

                    Back to the docs.

                    djl

                    Comment


                    • #11
                      RE: V5 beta FoxPro CDXs

                      erase all the $$*.mpx files in your a5v5beta directory and any that might be in your data directory. that's where the queries reside. the last queries also are in the registry, but you probably don't want to mess with that if you don't have to. there is also an option in a5v5 to remove all temporary queries when exiting a5. it's in view/settings somewhere.

                      Comment


                      • #12
                        RE: V5 beta FoxPro CDXs

                        if the foxpro table has indexes then you can select the tag in the index that you want to set as your "primary index" (i.e. the index that controls the record order) by clicking the "select index/query" button on the toolbar, or clicking "ctrl I".

                        however, you can also let a5 use indexes transparently for you. i.e. if you have index on "lastname" and you give focus to the lastname field (while you are in a form view or browse view) and you click the "quick sort" icon, then a5 will "sort" the data instantaneously becuase all that it is really doing is making the "lastname" index tag active.

                        Comment


                        • #13
                          RE: i have never heard of an a5 user doing this.

                          I have occassionally used this feature (alternate index files with a different name than the table) to create temporary indexes for things that are done infrequently.

                          I believe the reason I did this was to keep the production index as small as possible. Dropping an index does not actually remove it from the index file. It just marks it deleted similar to deleting a record without packing the table. To fully remove the index, the whole index file must be rebuilt and that can take significant time.

                          Comment

                          Working...
                          X