Efficient from the aspect of the guys who run the servers, but from the guys who are making DB's and using Access heavily, 97 is much quicker. As for running 2 versions, it's easy to do when your talking Access97. You need to install it after 2003 and then change the MDB associates back to 2003 as you please. I have decided not to install 97 on my servers for the 3 users that need it, but I have the option of letting them still run it on their desktops becaue they are fat clients. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Schneider, Chad M Sent: Tuesday, November 01, 2005 8:31 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Content Redirection Thanks. If I had a choice, it would be ONLY be Access 2003, as it is MUCH more efficient than 97. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Wood Sent: Tuesday, November 01, 2005 7:22 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Content Redirection Don't think so - Server to Client is only for URLs I suppose you could publish the content. This isn't pretty mind - easier to live with the Access on the server. If you're concerned about running different versions of Access on a single box do some searches through Rick's posts - -he's described some neat methods of getting multiple versions of access running on the same server for users. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Schneider, Chad M Sent: 01 November 2005 13:12 To: thin@xxxxxxxxxxxxx Subject: [THIN] Content Redirection I have an application that pulls MDB's. Rather than have Access (97 is required) on the server, I would like to use content redirection so that if an MDB is encountered, it attempts to open with the local install of Access on the client machine. Is this possible?