Silicon Investor (SI) -- The First Internet Community

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 -- Ignore unavailable to you. Want to Upgrade?

To: Jeff Redman who wrote (1032)	12/19/1998 9:14:00 AM
From: Daniel	Read Replies (1) \| Respond to of 1361

<"solve the problem by deleting the bad record"> Certainly not TEOTWAWKI. What would that record be, a transaction?. Something that did not get billed to my credit card? Great! What if you have to delete a couple of thousand records. Surely this causes some degree of disruption. Some shops will be more sensitive to disruption than others, right? We are so "just in time" oriented, I think even small glitches will cause problems.

To: Jeff Redman who wrote (1032)	12/19/1998 3:27:00 PM
From: J.L. Turner	Read Replies (1) \| Respond to of 1361

Mr. Redman, I think I understand your defining a bug as opposed to a virus.I even agree with your analysis as far as it goes.What I don't understand and what you have not addressed is this: You will not know if your suppliers are compliant until after the fact.You[a company] could receive bad data from one source or from multiple sources.The amount of problems could be greater than your staff could handle[especially short term].Then you have to deal with residual failures[By the way what is the residual rate for your company?]Then the power goes off.If any one let alone all three of these contingencies happen at the same time what do you do? This is not hype.Please don't hide behind that mantra.Either explain why:1Your suppliers will all be compliant. 1b there will be no residual failures or 1c The power cannot fail.If you can't explain the above what contingency plans would be in place.After all in your prior post you refer to bad data causing you to delete and restart.How does one restart without power?What if your bad data was hundreds of entrys or thousands?Would this not cause your company to try and reorder from your suppliers thus compounding the problem? J.L.T.

To: Jeff Redman who wrote (1032)	12/19/1998 8:11:00 PM
From: Jim	Read Replies (1) \| Respond to of 1361

Jeff: Just put these statements in your input program: IF LEN(YEAR) = 2 THEN IF YEAR LT 80 THEN YEAR = 20:YEAR ELSE YEAR = 19:YEAR END Where do I send my consultant invoice?

To: Jeff Redman who wrote (1032)	12/20/1998 11:43:00 AM
From: Sawtooth	Read Replies (1) \| Respond to 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.