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

A4V3 dbf not recognized by dBaseIII

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

    A4V3 dbf not recognized by dBaseIII

    Until recently I could create a new database file and have it recognizable and useable by dBaseIII. The only thing that has changed is the computer on which the database file is created. When an attempt to access the database file in dBaseIII is made, the message 'this is not a dBase file' appears. Am I now missing a link from Alpha4V3 to dBaseIII?

    #2
    RE: A4V3 dbf not recognized by dBaseIII

    I have not used dbase III, however in your default settings, there is
    an option to set for dBase IV compatability. Yes or No option. This
    might make a difference whether dBase III can read the database.

    Comment


      #3
      RE: A4V3 dbf not recognized by dBaseIII

      This is the same problem I'm having. Years ago I wrote some programs using DBXL, a II clone at the time, and have used them to analyse my A4v6 DB files. At some time in the
      near past, my pgms stopped reading the DB files...same problem as yours.

      Have anyone come up with the reason? And the fix? Thanks.

      Comment


        #4
        RE: A4V3 dbf not recognized by dBaseIII

        Guys,

        Mr. Spencer has it partially correct. In choosing DBase III or Dbase IV compatibility, it must be one or the other. Choosing DBase IV will exclude you from reading DBase III files in Alpha4, at least in the Vs2 and Vs3 of Alpha 4.

        I do not know if DBase IV compatibility was previously chosen how or if you can go back to making it DBase III compatible.

        Comment


          #5
          RE: A4V3 dbf not recognized by dBaseIII

          Dave,

          Yes, Dbase III and DBase IV are not compatible and consequently it makes a difference in choosing in Alpha4. I have stayed with DBase III compatibility with A4 V2.1 for these years without a problem.

          Since I am not familiar with these options for later A4 versions past V3 I do not know when or if these choices were changed for choosing compatible .dbf formats. with A4

          Comment


            #6
            RE: A4V3 dbf not recognized by dBaseIII

            Hello!

            >> Until recently I could create a new database file and have it recognizable and useable by dBaseIII. > the message 'this is not a dBase file' appears > This is the same problem I'm having ... using DBXL

            Comment


              #7
              RE: A4V3 dbf not recognized by dBaseIII

              My belated but heartfelt thanks for leading me to this solution. Thank you for the help. It is much appreciated.

              Comment


                #8
                RE: A4V3 dbf not recognized by dBaseIII

                David:

                Glad it worked for you!

                O.J.

                Comment

                Working...
                X