Ask a Question related to Coldfusion Database Access, Design and Development.

  1. #1

    Default Re: FoxPro ODBC problem

    Hank,

    We have similar problems. Our traffic load is relativley heavy and we have to
    reboot the server sometims 3 or 4 times a day. We haven't been able to find a
    solution yet.

    Have you found a solution?

    Thanks,
    Mike

    mletson Guest

  2. Similar Questions and Discussions

    1. Postgresql Text field / Visual FoxPro Memo and ODBC
      On Wed, 2005-01-12 at 14:59, MargaretGillon@chromalloy.com wrote: Postgresql doesn't support updatable cursors. ---------------------------(end...
    2. ado and odbc problem
      I install a update to date ODBC and running following code to connect with DSN and get following error. My server binds with 2 IP and hosts 2...
    3. [Microsoft][ODBC Visual FoxPro Driver]Cannot update the cursor.
      Hello, I contstaly run into the same error when trying to update a .dbf table with asp. Cannot update the cursor. We have vfp application...
    4. ODBC Problem!
      I have just installed a new IIS Server and implemented security restrictions on it using the IIS Lockdown tool. I am now getting an Internat...
    5. ASP, Access 2000, Visual FoxPro, ODBC Error
      Hi, I have a Visual FoxPro database named C:\Test\VFP\DB.DBC. This database has a single table in it Address.DBF. The Address.DBF table is also...
  3. #2

    Default Re: FoxPro ODBC problem

    If you need a type 4 JDBC driver, try [url]www.hxtt.com[/url].

    We've tested their MS Access drivers but not the Foxpro.

    Stephen Dupre
    Macromedia QA
    sdupre Guest

  4. #3

    Default Re: FoxPro ODBC problem

    Originally posted by: sdupre
    If you need a type 4 JDBC driver, try [url]www.hxtt.com[/url].

    That was the solution we settled on, sort of...

    We found that the HXTT FoxPro driver works perfectly for reads, but is
    unpredictable for inserts and updates, so we use it only for reads. For writes,
    we use the old Microsoft ODBC driver in single-threaded mode -- it's relatively
    slow, but writes are such a small percentage of our activity that it presents
    no problems for us. We've been operating in this mode for more than six months,
    during which time we've basically experienced no problems. It seems like a
    bizarre solution, but it's worked quite well for us.

    BY the way, the folks at HXTT are probably the most responsive support people
    I've ever met. They haven't implemented every last FoxPro function in their
    driver, but every time we need to use a function that they don't support, we
    ask them about it and they implement it within 24 hours, at no extra charge. I
    have a feeling that they could have resolved the problems we experienced with
    writing to FoxPro tables if we had worked with them, but the solution we
    implemented works for us so we didn't want to take the time to do that. I can't
    say enough about their responsiveness, despite being halfway around the world
    and not speaking great English, they're wonderful to work with.


    HankM Guest

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139