Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

we work in Visual FoxPro


  • Please log in to reply
2 replies to this topic

#1 EstelleThiers

EstelleThiers

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:14 AM

Posted 27 November 2017 - 12:11 PM

Today has unexpectedly stopped opening database via FoxPro. I've appealed to urgent help to our company's tech support, but of course they couldn't help me, because of theirs bad condition after weekend.



BC AdBot (Login to Remove)

 


#2 RecursiveNerd

RecursiveNerd

  • Malware Study Hall Junior
  • 224 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Louisville, KY
  • Local time:05:14 PM

Posted 01 December 2017 - 03:32 PM

What error message are you getting?



#3 samuelmina

samuelmina

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:14 AM

Posted 02 December 2017 - 10:11 AM

First one there is method from my friend-programmer

 

If you have access to Visual FoxPro command line window, type:

SET TABLEVALIDATE 11

USE "YourTable" EXCLUSIVE    && If the table is damaged VFP must display an error here

PACK && To reindex the table and deleted "marked" records

PACK MEMO && If you have memo fields

After doing that, the structure of the table must ve valid, if you want to see fields with invalid data, you can try:

SELECT * FROM YourTable WHERE EMPTY(YourField)   && All records with YourField empty

SELECT * FROM YourTable WHERE LEN(YourMemoField) > 200   && All records with a long memo field, there can be corrupted data

 

Otherwise, there are following effective articles and materials right there if your database is not a database file in foxpro:

 

https://support.microsoft.com/en-us/help/193952/how-to-troubleshoot-to-resolve-suspected-corruption-in-visual-foxpro

http://fox.wikis.com/wc.dll?Wiki~TableCorruptionRepairTools






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users