Results 1 to 5 of 5

Thread: Dbase memo field

  1. #1

    Thread Starter
    New Member
    Join Date
    Sep 1999
    Posts
    2

    Post

    How do access a dbase memo field using VB5 & RDO.

    I can access the rest of the table/.dbf file and I know that the memo data is stored in seperate .dbt file, BUT HOW DO YOU GET TO IT..

    Any help appreciated.


  2. #2
    Hyperactive Member scuzymoto's Avatar
    Join Date
    Aug 1999
    Location
    Washington State
    Posts
    316

    Post

    VB has some real troubles using anything that is DBase or XBase. Jet can't handle cdx style indexes nor many other vital parts of Xbase. One of which are memo fields. You will probably have to look into a third party product to patch your VB code, at least thats the route we took. Probably the best out there right now, though I have varied complaints about it, is Artemis. Its big brother Apollo works great for Delphi but Artemis for VB is passable. Try this link for more information... http://www.vistasoftware.com/

  3. #3
    Hyperactive Member
    Join Date
    May 1999
    Location
    Reynosa, Mexico
    Posts
    274

    Post

    I'm currently working in a proyect accesing to FoxPro files with RDO and ADO. As it also are .DBF, may be I can help you.

    Please explain as deep as posible your problem with memo fields. Include the SQL line which open the ResultSet, etc.

    If you wish, you can email me your proyect (and your database) to try to reproduce the problem and look for a good solution.

    Office 2000 brings a new ODBC driver to dBase and Visual FoxPro which seems to solve the problems with the memo (and numeric) fields.

    Good Look!

    Ulises
    [email protected]

    [This message has been edited by Tonatiuh (edited 10-01-1999).]

  4. #4
    Addicted Member
    Join Date
    Sep 1999
    Location
    Philippines
    Posts
    196

    Post

    Try getting only the memo field alone in a sql statement.

    eg Select memofld From Table where condition.

    Hope this helps.

  5. #5

    Thread Starter
    New Member
    Join Date
    Sep 1999
    Posts
    2

    Post

    Thanks for all the replies.

    It seems that the files I'm accessing are not pure DBase files but some obscure variant.

    The new Office 2000 Odbc drivers apparently do fix my current problem.

    However due to time pressures I have implemented a DAO solution, which works perfectly well.



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width