Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Error Handling in Scan Endscan Loop
Message
From
31/01/2014 06:47:06
 
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8
Network:
Windows XP
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01592536
Message ID:
01592736
Views:
50
>>I have a SCAN-ENDSCAN loop with Millions of records in between. The records are infact the name of Files like C:\Bills\1.txt,c:\bills\2.txt.
>>
>>The code between takes the files and edit the TXT files as per my requirement.
>>
>>Generally Things go fine, however sometimes there are files with error inside TXT files only and my code does not satisfy the condition and therefore gives an error window like
>>
>>CANCEL,SUSPEND,IGNORE.
>>
>>At this time I Select IGNORE and my process goes further to the next record.
>>
>>Is there anyway by which is during course of SCAN ENDSCAN Error occurs, it should automatically IGNORE and move to the next record. so that I have not to wait infront of the screen for contionious monitorng
>>
>>If yes, kindly provide the piece of that Code.
>>
>
>Hi, I read through all the replies, and certainly TRY....CATCH is significantly better than ON ERROR.
>
>Just something to think about - assuming your company is also using SQL Server - take a look at Integration Services (SSIS). It gives you some great capabilities for extracting data from one area and loading it into another. I actually have some training videos on SSIS if you're interested.
>
>
>If you're not using SQL Server, then no need. But if you have it, and if you even periodically take data from one source, do something with it in between (and also send error rows to an exception file), and then load it to another destination, you might find some of the features in SSIS to be quite powerful.

Kevin,
I like to know more about SSIS and how it can be used in a business application with a SQL Server backend. I always thought for more complex sql tasks stored procedures are the way to go, and the rest with regular sql statements.
Christian Isberner
Software Consultant
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform