Re: Witango-Talk: Weird

[Web Dude]

Well it seems to be working, but I am not sure why. Maybe one of the records I deleted was corrupt. But I must say that during the past year, I have had taf files suddenly stop working and go corrupt for no reason that I can fathom. When run they will take up 100% of the CPU and bring both the Watango server and the SQL 7 server down (both machines). The only way to fix is to rewrite the taf from scratch again. This has happened to me 3 times now. I come in the morning and both machines are running extremely slow. I can go through the Witango log files and find the entries that KILL the process. That shows me which taf is screwing up. Next I go and redo the taf file from scratch and everything works fine. Very random and 2 of these tafs have not been touched for at least a year. It drives me nuts, but it is fixable.

Anyone else have anything like this???

What happens if you check distinct rows. Does that fix the problem.


--
Dan Stein
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Mobile: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000
[EMAIL PROTECTED]
www.dss-db.com

 From: Web Dude <[EMAIL PROTECTED]>
 Reply-To: [EMAIL PROTECTED]
 Date: Tue, 17 Dec 2002 11:56:02 -0500
 To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]>
 Subject: RE: Witango-Talk:  Wierd

 I am using Microsoft ODBC version 3.520.6019.0
 Microsoft SQL Driver 3.70.09.01
 This seem very strange. I have product tables that have thousands of
 records that I can search with multiple pages with no problems. I
 checked the Witango log files and noticed that I am getting a log
 entry...

 KILLED         E:blahblah/whatever/searchcustomers.taf

 after a while and the thread pool size is way up there (650,000 give
 or take). Sounds like a loop, but I built this straight from the
 search builder several times with test tafs.

 I went through the table and deleted all duplicate records and got
 the table down to 850 rows and...

 NOW IT WORKS?!?!?!

 It appears that if I want to show a return list with multiple pages
 (next and previous buttons) this table bombs if I have over 1000 rows
 in it. Very strange. If I have under a thousand, it appears to work
 fine...

 Any suggestions????

 Do you have a non-Witango ODBC client that you can use to run the same SQL
 expression? It might help narrow down the source of the problem. Just make
 sure that it is using the same ODBC data source.

 Hope this helps,

 Steve Smith

 Oakbridge Information Solutions
 Office: (519) 624-4388
 GTA:    (416) 606-3885
 Fax:    (519) 624-3353
 Cell:   (416) 606-3885
 Email:  [EMAIL PROTECTED]
 Web:    http://www.oakbridge.ca

  -----Original Message-----
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Web Dude
  Sent: December 17, 2002 10:54 AM
  To: Multiple recipients of list witango-talk
  Subject: RE: Witango-Talk: Wierd


  Sorry...

  SQL 7 - latest sp's on a separate server NT 4.0 sp6a

  I am currently weeding out duplicate entries in the customer table.

 Did you mention what you are using for a database server?

 Please let us know.

 Thanks,

 Steve Smith

 Oakbridge Information Solutions
 Office: (519) 624-4388
 GTA:    (416) 606-3885
 Fax:    (519) 624-3353
 Cell:   (416) 606-3885
 Email:  [EMAIL PROTECTED]
 Web:    http://www.oakbridge.ca

  -----Original Message-----
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Web Dude
  Sent: December 17, 2002 10:13 AM
  To: Multiple recipients of list witango-talk
  Subject: Witango-Talk: Wierd


  Witango 2000
  NT 4.0
  sp6a
  IIS

  I have a customer table that has around 1600 records. It has around

 >>>>>  25 columns with various info (last name, address, ship address,

  phone, etc.).

  When I build a search and search for all records, Witango bombs. It
  takes up 100% of the CPU and just spins. I have taken this exact same
  search and search a different customer table (Same columns different
  database) with only around 350 records, and it works fine. If I click
  off the get total rows it works fine, but of course I cannot scroll
  to next or previous pages. It is almost as if Witango can't take the
  return of all the rows in the list.

  I have tried building a simple search with multiple page results
  searching for just the last name and I get the same result.  Bomb
  City. Is it possible that the returning list is too large? And is
  there a place I can go to fix this?

  First time I have ever encountered something like this. Could the
  Table be corrupt. Is there something in the config I need to adjust?

  Thanks...
  --

  ________________________________________________________________________

  TO UNSUBSCRIBE: send a plain text/US ASCII email to

  [EMAIL PROTECTED]

                  with unsubscribe witango-talk in the message body

 ________________________________________________________________________
 TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                 with unsubscribe witango-talk in the message body

  --
  ________________________________________________________________________
 TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                  with unsubscribe witango-talk in the message body

 ________________________________________________________________________
 TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                 with unsubscribe witango-talk in the message body

 --
 ________________________________________________________________________
 TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
               with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

--
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
               with unsubscribe witango-talk in the message body