On Apr 06, 2007, at 20:53 UTC, Giovanni wrote: > On 2, the reason personally that I got frustrated is because our > entire group of apps worked on R1 and no longer works on R2, not > without any modifications anyhow. I am also familiar, being with MS > tools that some fixes can sometimes crash a system, however.
I'm not sure exactly what modifications you're needing (I haven't read this whole thread), but FWIW, in my case the only common one I had to make was the many places I was using "New Date.TotalSeconds" or "New Date.SQLDateTime" or similar (to get a property of the current date/time). This no longer works, due to an intentional change that's needed for some upcoming functionality (something about "namespaces" may have slipped into the release notes, giving us a clue). So, I found it helpful to define a new global function like so: Function NewDate as Date return New Date End Function Then I can simply search and replace every "New Date." with "NewDate." I'm aware that for many of us on this list, it's harder than perhaps it should be to get a date. But with this technique, I think you'll find it easier than ever! HTH, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
