2000 Date-Change Problem: Scam, Hype, Hoax, Fraud Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : 2000 Date-Change Problem: Scam, Hype, Hoax, Fraud

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Jeff Redman who wrote (1032)	12/20/1998 11:43:00 AM
From: Sawtooth	Read Replies (1) of 1361

<<I'll get a call if my program goes down, sometimes I solve the problem by deleting the bad record, then restart the job and it completes.>> Interesting discussion here; hope I can jump in. How does your program know a "bad" record from a "good" record if the "bad" data passed to you is within the parameters of your control system, ie. looks like any other "good" data? <<The bad record did not effect the other data in the file, or data from another store or cause the program to be contaminated.>> What if you don't catch the "bad" data before you interface with and update another system(s), within or outside of your organization? TIA.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next