Script no longer works after Upgrade to 10.4.6

Question

The following script worked fine using 10.4 thru 10.4.5 but no longer works after upgrading to 10.4.6.
When I highlight a folder and then run the script the highlighted folder is moved to a specific "Achive" folder, depending on whether the highlighted folder has a ".0" or ".1" or etc in its name.
When I run the script using 10.4.6 I get an error indicating that the highlighted folder already exists in the destination.
Anyone else having Applescript problems with 10.4.6?
--Bob
tell application "Finder"
activate
set fname to selection as string
if fname contains "0." then
move selection to folder "ARCHIVE" of folder "0JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "1." then
move selection to folder "ARCHIVE" of folder "1JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "2." then
move selection to folder "ARCHIVE" of folder "2JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "3." then
move selection to folder "ARCHIVE" of folder "3JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "4." then
move selection to folder "ARCHIVE" of folder "4JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "5." then
move selection to folder "ARCHIVE" of folder "5JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "6." then
move selection to folder "ARCHIVE" of folder "6JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "7." then
move selection to folder "ARCHIVE" of folder "7JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "8." then
move selection to folder "ARCHIVE" of folder "8JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
else
if fname contains "9." then
move selection to folder "ARCHIVE" of folder "9JobsArchive" of folder "Archived_Files" of disk "Preflight_Only"
end if
end if
end if
end if
end if
end if
end if
end if
end if
end if
end tell

Answer 1

I, too, immediately started having problems with my scripts immediately after updating to OS 10.4.6. I put my scripts in "Library/Applications/..." so that the scripts associated with particular applications are available in the menu bar. I don't know if that has any bearing on the problem, but for me, it was not any particular script, but just about every one that started going funny.
First, I noticed that my scripts would typically work right once, but fail in some odd manner the second time I tried to use one. The second thing I noticed was that the modification dates of my scripts were changing to the time that I last executed the scripts, even though I had not altered and recompiled any of them in weeks. Finally, I noticed that the scripts that were failing were ones in which I had used property statements to initialize some of my variables.
What I think is happening is this: for some strange reason 10.4.6 is recompiling scripts every time they are run, and variables are being initialized, not to the values specified in property statements, but to whatever the variable was the last time the script ended.
I discovered that I could prevent this from happening by (1) recompiling all my scripts to make sure all the property statements were back in effect, and then (2) setting the permissions of all my scripts to read only. This seems to prevent whatever in 10.4.6 is recompiling the scripts from doing this each time the script is run. At least, the modification dates are no longer changing inexplicably, and all my scripts are running reliably again.
It's a bit of a pain to have to remember to reset script permissions to read/write whenever I want to make a change, and then change them back to read only before executing, but it seems to be a reliable workaround. I'd appreciate hearing if anyone else can replicate this phenomenon, or tell me if I'm on the right track.
Jeff Johnson
Dual 1.2 GHz   Mac OS X (10.4.6)  
Dual 1.2 GHz