Search results for query: *

Well.. My problem is likely different than yours. But google led me to this post to solve my problem. I just posted my solution so some other lost soul (other than myself) could find help! Sera Sera

I just solved this problem using Tie::File. It was the only way I could correctly insert a new line into a file. In my case I needed to replace the first line. use Tie::File; tie @anArray, 'Tie::File', "afile.csv" or die "can't open"; #Deletes the first line in the file shift(@anArray)...

Leave it to me to find wrong results...I am pretty good at that! Sera

Well let that be a lesson to me....lazy coding style gets you lazy results.... Thanks Guys! Sera

Whoa...it is the datatype.... When I do this it works --note varchar is exactly the the same size as the string Declare @fileAbbr As varchar(5) Set @fileAbbr = 'PHEV1' --returns 105 records Select * From FileInfo Where FileName Like @fileAbbr + '%' --returns 105 records Select * From FileInfo...

FYI I tried your example and it performed correctly.... Sera Sera

Declare @fileAbbr As varchar Set @fileAbbr = 'PHEV1' --returns 229 records Select * From FileInfo Where FileName Like @fileAbbr + '%' --returns 105 records Select * From FileInfo Where FileName Like 'PHEV1%' Sera

Is it possible that I am declaring the @avar incorrectly? DECLARE @avar As varchar Sera Sera

Sorry bborissov...I didn't read the whole message. I dunno what you mean by...create a repro code? I am really looking for someone to tell me this has happened to them before...and this is why. It really is as simple as my explanation I promise. The first example returns 24 records The...

Yes I am sure! Sera Sera

I am getting incorrect results from my query. If I write the query like this I get too many results: set @var = 'matchstring' select * from table where aval Like @var + '%' If I write the query like this I get the correct results: select * from table where aval Like 'matchstring%' ....I...

slepnir214 : Yes they do all use "Location" header. jpadie: interesting idea. It is true that the two machines are vastly different. The 2003 server is most definitely faster than the 2000 server. A race condition is probably occuring. I am sorry if I haven't said it clearly or at all...

Well if it transmits the cookies by default then yes. We are not explicitly using set_cookie(). We are setting the value inside the session. Sera

I would like to show everyone that numerous people have had this problem.... http://bugs.php.net/bug.php?id=14636 Sera

Now that sounds promising. He is using header(Location: "someurl.php"). We are not using cookies tho, and I am not really sure how to apply that particular link to our problem. But it does give me somewhere to look. Jpadie: The code is numerous pages connected to each other. Way too much...

Well I know you are saying it should be ignoring them, but its not. I watch the sessions get created in the sessions folder each time we load the page. I know the way php sessions are supposed to behave, due to my two days of searching the internet trying to find someone else who has had this...

Hmm, well I dunno what to think. The permissions match across all of the directories. The temp directories and the data directories. I can reproduce the erratic behavior on the Server 2000 box. The Server 2003 box just doesn't care. The website uses .shtml pages so that it can conform to...

Well there is another key point. It works all of the time on IIS 6.0 and doesn't really work on 5.0 Does anyone know if/how sessions are handled differently between the two....? My intern built the application that I am trying to fix, we have decided that he is going to have to re-architect...

The permissions are the same. The key point here is that SOMETIMES it works - hence it can read and write SOMETIMES it doesn't I know that doesn't make sense but I promise that is what is going on. Sera

Hello, I have a really weird problem. I have been googleing for hours. We have a website with multiple pages accessing one session. We use session_start() on every page. Everything works fine on Windows Server 2003, however when we migrate it to our Windows Server 2000 box the session...