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



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

DAO, ADO and all that stuff

  • Filter
  • Time
  • Show
Clear All
new posts

  • DAO, ADO and all that stuff

    I am trying to link my A5 database to my MSWord97 projects and am having a devil of a time doing so. I want to keep A5 for collecting and reporting data (because it is so easy), but do document writing and assembly with via Word. I have accomplished an effective, but rather slow link to my data via ODBC, but want to try to implement connections to what I understand are more powerful linking tools of DAO and ADO.

    My problem is in the initial coding. I cannot get the database to open. An answer to the following questions may help. Is the .dbf or is the .adb file the parallel to the .mdb file used by Access. (I ask because all of the examples given in the book I am using pre-suppose an .mdb file, even though the Microsoft.Jet programs profess complete compatibility with .dBase style files.

    I have DAO 3.51 Object Library loaded and registered. This is my code in the macro which I have written, following the examples given, to open up the database.

    Const connectStr = "PROVIDED=Microsoft.Jet.OLEDB.3.51;Data Source=C:datadatabasesdomstuff.dbf;"
    Dim myConnect As New ADODB.Connection
    Dim myRS As New ADODB.Recordset
    With myConnect
    .ConnectionString = connectStr
    .ConnectionTimeout = 10
    End With
    When the .Open command is executed, I get an error, saying "DataSource name not found and no default drive specified."

    What's missing? Thanks for any help.

    Roy Lasris

  • #2
    RE: DAO, ADO and all that stuff

    Sounds as though you want to connect to the DBF using VisualBasic. Or the scripting language built in to Word. Can't help you with either. You might try newsgroups devoted to VisualBasic and databases. I suspect that VB programmers are very familiar with the steps necessary to connect to dBase or FoxPro files. I think A5 uses a format that's compatible with Foxpro 2.6

    -- tom


    • #3
      RE: DAO, ADO and all that stuff


      I'm somewhat new to VB (VBA with Word), but some of what follows might help.

      You can find the code to connect to a variety of databases through either DAO, Microsoft's older connection technology, or with ADO -- supposedly newer, better and headed for world database domination (at least in the Microsoft/VB/VBA realms).

      ADO is an easier connection to make, but handles xBase file operations very slowly. The DAO connections seem to be much faster when running through the same operations.

      For Alpha Five connections, try connectiong to the ****.DBF file using either a FoxPro or dBase III specification.

      Make sure that you have the most current ODBC drivers from Microsoft.

      Good luck...


      Geoff Hollsnder