DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: VFP ODBC, Error -2147467259, Run 30UPDATE.PRG

  1. #1
    Paul Jones Guest

    VFP ODBC, Error -2147467259, Run 30UPDATE.PRG


    We often get this error when we use ODBCs pointing to DBCs and two users try
    to open an ADO connection simultaneously - one of them fails.
    Having trawled the internet for a solution, I've found only an obscure support
    article from Microsoft confirming that this is a bug. They suggest merely
    trapping it in an error routine and doing an infinite number of retries.
    Having recreated this error in code, I've discovered that the 'retry' only
    works once the 'dominant' connection is finished, so this is useless - our
    application can have multiple users opening and closing these connections
    throughout the day, and this much traffic is bound to cause several pile-ups!
    Configuring the ODBC to point to a drectory instead never fails - are there
    any drawbacks to using this method instead of the DBC one, or does anyone
    know how to fix the original problem?

  2. #2
    Dan Freeman Guest

    Re: VFP ODBC, Error -2147467259, Run 30UPDATE.PRG

    I've *always* connected to a directory because it's the only way to get to
    free tables.

    Dan

    "Paul Jones" <paulj@advatech.co.uk> wrote in message
    news:3f17c3c9$1@tnews.web.devx.com...
    >
    > We often get this error when we use ODBCs pointing to DBCs and two users

    try
    > to open an ADO connection simultaneously - one of them fails.
    > Having trawled the internet for a solution, I've found only an obscure

    support
    > article from Microsoft confirming that this is a bug. They suggest merely
    > trapping it in an error routine and doing an infinite number of retries.
    > Having recreated this error in code, I've discovered that the 'retry' only
    > works once the 'dominant' connection is finished, so this is useless - our
    > application can have multiple users opening and closing these connections
    > throughout the day, and this much traffic is bound to cause several

    pile-ups!
    > Configuring the ODBC to point to a drectory instead never fails - are

    there
    > any drawbacks to using this method instead of the DBC one, or does anyone
    > know how to fix the original problem?




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center