Below are the 2 most recent journal entries recorded in magera227's InsaneJournal:

Tuesday, December 6th, 2011
6:34 pm	Drug reviews: asthma inhaler advair linked to rise in mortality from symptoms of asthma Advair, combining salmeterol (Serevent) and fluticasone (Flovent) is one of the best selling drugs in the world buy coreg online without a prescription. Salmeterol is often a bronchodilator which dilates the airways and fluticasone is a steroid which reduces airway inflammation. However, the drug is here under scrutiny as a result of recent report that Advair may possibly increase asthma deaths. Producer GlaxoSmithKline, however, has rejected the findings and calls this content extremely irresponsible and riddled with inaccuracies. Forbes magazine been in a short article on 6th April, reported that "growing evidence suggests that a small % of patients--perhaps 4,000 people 12 months, by one doctor's estimate--may be dying due to Advair or its Serevent component". It quotes Dr. Shelley Salpeter, a clinical professor of medicine at Stanford University who argues who says both Advair and Serevent should be recalled. Dr. Shelley reviewed the final results of 19 previous trials of Serevent-style drugs and located that patients have twice the rate of asthma hospitalizations, twice the speed of life-threatening asthma and four times as many deaths as patients whorrrre not on those drugs. Apparently, Advair and Serevent cause four of each and every five asthma-related deaths each year. "These drugs make asthma worse," Dr. Shelley says. By some estimates, asthma kills roughly 5,000 Americans annually. This extrapolates to 4000 asthma deaths associated with these drugs. In response, Glaxo says its detractors are exaggerating the potential for loss. "The safety and efficacy of Advair can be extremely well-established with regulators and physicians around the globe," A Glaxo spokeswoman said. "The data we've are inconclusive," says Kathy A. Rickard, a Glaxo v . p . , echoing early responses by Wyeth about its Redux diet drug and Merck & Co. about its Vioxx painkiller. Last month GlaxoSmithKline had reached an agreement using the U. S. regulator to update Advair's label with a brand new warning advising doctors to limit the application of the drug to patients that do not reap the benefits of other asthma drugs, or that are severe cases. Current Mood: nauseated (Comment on this)
5:40 pm	Repeater failure and disappearance on row 28 ellis web development Posted on August 2, 2007 at 10:47 I was working on an ASP. net application (1. 1) the other day, changing the UI display of your page. This article basically contained a Repeater being populated with data from the DB, and binding javascript actions and styling info towards the different rows to become output (each overall that it was putting together a Table, and every item would have been a TableRow). Even though look-and-feel would be changing, as well as the procedure by which the info ended up being be retrieved, your data set up and binding ended up being remain the same because it had been. Piece of cake, right The programming was straight-forward enough. When I first tested the feature with a few records, it worked fine. However, when I tested it on more records, it have not. And once I believe that so it didn't work, I am not saying which i got in some ugly . Net exception. After all how the HTML output because of the server was completely devoid of the Repeater element. It turned out just as if it really wouldn't exist. Somehow, while i tried the stress the page with a large numbers of records, some weired thing happened in IIS that merely completely abandoned the rendering with the Repeater element without providing one message. Completely weird. After a few hours of debugging, I'd been capable to determine how the error has not been in connection with any sort of data item. Rather, it always happened when outputting the 28th DataItem from the Repeater. 27 worked fine. levitra online no prescription 28 killed it. Racking my brain (and Google), I could not find any reason why this may be happening. This identical repeater worked fine on other pages, about the live site. There was clearly pointless I really could imagine why this kind of failure would happen, and why it would happen here. My coworker SeanS suggested that perhaps i thought this was in connection with my dev environment, perhaps some faulty memory as well. There was hardly anything else to go on this also did explain the concepts going on (and that i knew that this feature worked for <28 rows), so I proceeded with development. And lo and behold, when I uploaded my changes to the staging site yesterday, it worked with any number of rows without any hitch-up. Moral from the story: weird the unexpected happens on web servers and on dev machines. Don't assume all error that you will get relates to code (particularly if the error is reported through the absence of output as opposed to an exception). If something similar to this is affecting you (and it is not reproducible on other platforms), it could be environment-related. Test this out before wasting more hours as well as wanting to get it sorted out from the code. Current Mood: predatory (Comment on this)