Microsoft Knowledge Base Email Alertz

KBAlertz.com: Files with ActiveX Controls that are saved in Office 2007 format change to images when opened in Office 2003 with the compatibility pack installed

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 200025 - Last Review: October 15, 2003 - Revision: 2.1

PRB: Erroneous Error When Repeatedly Opening Database

This article was previously published under Q200025

SYMPTOMS

If you open a database located on a server numerous times from multiple Visual FoxPro 6.0 executables, then the following error randomly appears:
This file is incompatible with the current version of Visual FoxPro. Run 30UPDATE.PRG to update the file to the current version.
This error may also occur if you are opening a Visual FoxPro 6.0 database using ADO or the Visual FoxPro ODBC driver.

RESOLUTION

Use any ON ERROR procedure, such as the one in the code example in the MORE INFORMATION section below, to trap for the spurious error.

MORE INFORMATION

This behavior does not occur in Visual FoxPro 5.0x.

Steps to Reproduce Behavior

  1. Set up a server machine and a client machine. Install Visual FoxPro 6.0 on the client machine.
  2. On the client machine, create a project and build an executable containing the following code:
       CLEAR
       ON ERROR DO Errorhandler WITH ERROR(), MESSAGE()
       KEY=0
       OPENED=0
       errored=0
       DO WHILE KEY=0
          OPEN DATA k:\robert SHARED
          OPENED=OPENED+1
          @1,1 SAY "Opened:" + STR(OPENED)
          @2,1 SAY "Errored:" + STR(errored)
          CLOSE DATA
          KEY=INKEY(1)
       ENDDO
       QUIT
    
       PROCEDURE Errorhandler (nError,  messx)
       errored=errored+1
       @3,1 SAY nError
       @4,1 SAY messx
       RETRY
       ENDPROC
    						
  3. From the client machine, use Windows Explorer and map a drive K that points to a shared folder on the server machine.
  4. Create a database on the K drive using Visual FoxPro 6.0. This database does not need to contain any tables.
  5. Go to the client machine and start at least four instances of the Visual FoxPro executable created in step 2 using Windows Explorer. You many need to start more instances to recreate the problem.
Depending on the scenario, the error may appear quickly or it may take several minutes.

APPLIES TO
  • Microsoft Visual FoxPro 6.0 Professional Edition
  • Microsoft Data Access Components 2.5
Keywords: 
kbdatabase kbpending kbprb KB200025
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Claton Report As Irrelevant  
Written: 6/23/2009 12:48 PM
The title of KBAlerts and the KB title do not match. There seems be an Error

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please