Adobe bridge CS5.5 cannot delete files

Question

Hi
I have latest version of Lion, and recently upgraded CS3 to CS5.5. All my files under my home folder are there to view in bridge and were ofcourse created under CS3.
If I select ANY file, I cannot delete it, or move it, or rename it, or do a batch rename.. Nothing, yet it I find it in my finder window, I can delete it.
If I create a new .ai file which would be with CS5.5 I CAN delete it. So I am wondering what permissions are not sufficient from CS3 to CS5.5 in bridge. I have spoken to Apple Tech and they advised me to change my home folder permissions for Everyone to read and write and apply to enclosed items. That didn't work.
I have heard there is an issue between Lion and Adobe, but not sure I buy that one. At the end of the day Bridge is just like a finder window, except it have more tools and more links to more adobe applications, but basically a file view window. Yet when I choose to view files in Finder I can delete them, except it will keep asking me to enter my user pword everytime with no option to remember it.
The only way of getting around this so far is to manually one by one is SAVE AS each file with a new file name.. no auto script option I can see of doing it so far.
I have ALOT of files, surely there is something I should be knowing after all these years.
HELP!
Dan

Answer 1

Thank you, SG, for clarifying which OS's this will work with.
I agree with Jennie - the beauty of "get photos from camera" is that it takes 2 steps out of the workaround you mention above. Personally, I'm okay living with 6.4.1, as I have an older camera. I won't be happy if one of the push updates re-updates me to 6.5 though. I wouldn't want to redo the reinstallation of the new version. This method will not work for any of my clients or students though - they normally can't comfortably follow the technicality of downgrading, and some have newer cameras and would need the 6.5 version. (I don't believe in betas for my clients, and neither do they, for the most part)
I guess I should thank Adobe - some of my clients have needed tech support to perform the downgrade (SO many people aren't comfortable technically), and some of my clients needed to be retaught the workaround SG mentions. Adobe's flub has actually made me a little money - which I'd rather not have to make this way.
SG's workaround does work and makes sense - but for my clients with hundreds of images at a time, who have to rename items, add copyright info, & etc., this more than doubles their work-time for the start of their workflow. I hope Adobe gets that GM version out soon.
BTW - this issue supports an argument I've hadfor years regarding "PUSH" updates. I always tell my clients and students not to do them until they research the update. Because of what I do, I do have to install them personally, but I'm grateful I'm comfortable fixing things myself.