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

DATDoc v5 (or Phoenix Doc) :)

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

    DATDoc v5 (or Phoenix Doc) :)

    Here is the old v1 Documenter, revived and recoded to work with version 5.

    Special thanks to Bill Parker for his patients and cooperation in my formulation of the readme.txt.

    Your feedback will be appreciated.

    Melvin Davidson

    #2
    RE: DATDoc v5 (or Phoenix Doc) :)

    Melvin

    There is nothing attached?


    Rick T

    Comment


      #3
      RE: DATDoc v5 (or Phoenix Doc) :)

      Hmmm,

      Thanks for pointing out the attachment didn't attach.

      Take 2.

      Comment


        #4
        RE: DATDoc v5 (or Phoenix Doc) :)

        A revised version. The only change is that the report for
        set structure now uses semi-graphical represntion for links
        and handles all the link-types.
        eg: many->many master->first, master->last, master->closet key.

        Comment


          #5
          RE: DATDoc v5 (or Phoenix Doc) :)

          I, too, remember the documentor from v.1 Handy it was.

          I have downloaded your documentor and attempted to use it to document a set's field rules. It comes back with the following error:

          Script: Field Rules line 19:
          dbh+table.open(docdbf_name)
          The system cannot find the file speciified

          It gives the directory location, then the file name: record.dbf

          It cannot find the file, because there is no such database linked with the set. 'Record' is the name of the set.

          Just for the heck of it, I tried running the documentor on another set and came up with the same results, i.e., the documentor attempted to find a dbf with the same name as the set.

          Solutions?

          Windy

          Comment


            #6
            RE: DATDoc v5 (or Phoenix Doc) :)

            Windy,

            I believe the reason you are getting that error is because
            the documentor program expects all tables, master and child, to be in the same directory as the database. In other words, it doesn't know about the path.

            Have you tried the trial version of Bill Parker's documentor that comes with A5? You get 5 free uses before you decide whether you want to buy it/

            Melvin

            Comment


              #7
              RE: DATDoc v5 (or Phoenix Doc) :)


              "Have you tried the trial version of Bill Parker's documentor that comes with A5? You get 5 free uses before you decide whether you want to buy it."

              Ah, no. How do I access it? I did not find it on the Alpha5 CD.

              Windy

              Comment


                #8
                RE: DATDoc v5 (or Phoenix Doc) :)

                Windy,

                When you install Alpha Five, there should be a subdirectory created called A5DOC. In there is the A5DOC.adb.

                Open you database in A5 as normal. In the control panel,
                click File, Database Properties, Libraries. Then click the Add button. Navigate to the A5DOC.adb and select it.

                In control panel, Select Code, then select the MainMenu script and run it.

                Make sure you read the A5DOCReadMe.Doc and the A5DOCManual.rtf _before_ you use it.

                good luck,
                Melvin

                Comment


                  #9
                  RE: DATDoc v5 (or Phoenix Doc) :)

                  Melvin,

                  Found it! Thanks!

                  Windy

                  Comment


                    #10
                    RE: DATDoc v5 (or Phoenix Doc) :)

                    Getting a strange error when I try to create an operation on a table inside a set in the presense of DATDoc.

                    The error makes mention of A_tbl update.

                    See small jpg of error.

                    Comment


                      #11
                      RE: DATDoc v5 (or Phoenix Doc) :)

                      No jpg was attached to your message.

                      Just check that the properties for all A5Doc tables
                      do not have read only.

                      Comment


                        #12
                        RE: DATDoc v5 (or Phoenix Doc) :)

                        I think that the problem wasn't with Datdoc but another table. Once I solved that problem DatDoc works fine. Thank you.

                        Did you ever update your security demo beyond the one in the archive???

                        Bo

                        Comment


                          #13
                          RE: DATDoc v5 (or Phoenix Doc) :)

                          Bo,

                          I advised you in my reply to the securityn demo that it is not updateed and that you can correct as advised in the reply.

                          Comment


                            #14
                            RE: DATDoc v5 (or Phoenix Doc) :)

                            Revised 08/18/2004 to correct minor problem with options.

                            Comment


                              #15
                              RE: DATDoc v5 (or Phoenix Doc) :)

                              Latest version with the following fixes.

                              1. Previous version was missing the report for set structure
                              2. Field name length increased to 32, which is A5 max
                              3. Verified as working with Alpha Five version 6

                              Comment

                              Working...
                              X