To be quite honest - I've never actually used the ASSERT Command before. And, I was just looking at the online VFP help on how to use it.
Then I saw your next reply here. Problem is - I think you have to know Which DBF/Index has the problem - but, I don't know where in the code the problem is happening - so - not even sure which Index is having the problem! -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Dave Crozier Sent: Thursday, September 27, 2012 10:08 AM To: [email protected] Subject: RE: A Debugging Problem... Using Assert with Indexseek() can help. I assume that the index you expect isn't found or is corrupted somewhere. Indexsee() does a find WITHOUT moving the record pointer so you can "look ahead" so to speak. Dave -----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of Kurt Wendt Sent: 27 September 2012 14:57 To: [email protected] Subject: A Debugging Problem... OK - this is driving me a little crazy - so, figured someone here might have a suggestion. We have this shipment Packing modification program. And, for a particular client - they have been having problems with the UCC # - which was due to previous Bonehead programmers here Screwing up and not doing proper Record Locking - and if multiple users do the Packing - they clash and get the same stored UCC Seq #. BIG problem indeed - causing Major Chargeback issues. But, alas - I digress... I updated this program - with a bunch of code - not only to do proper Record Locking - but, also to check the shipment - if it already has the UCC #'s in it - and verify they are good and not used within another Shipment. I made a Ton of program changes, and compartmentalizing code into procedures. And - I pull all the code I worked on Out of the main procedure - and turned it all into sub-procedures. But, wouldn't you know it - the problem is happening in the main procedure. The program crashes and complains about an Index Tag. I really have no idea where in the code the problem is happening. I've tried stepping thru the code - but, the problem is - this shipment has nearly 800 Boxes - and its really not viable to use the Debugger and keep skipping thru code like that - for obvious reason. I even put in a Breakpoint - but, it never hits that spot in the code before it crashes. So - any advice/suggestions on what I should do to track down this Bug - without having to keep Stepping thru the code - since its Killing me... Thanks, -K- Senior Developer Waitex Information System, Inc. P Save a tree. Don't print this e-mail unless it's really necessary. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/289ea162f5642645b5cf64d624c66a140e260...@us-ny-mail-002.waitex.net ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
