What part of the word "RESERVED" do they not grasp? "RESERVED" means it's RESERVED for a specific use.
When you go to a concert, and sit in a seat marked "RESERVED" you can expect that it's odds-on there's gonna be trouble, unless it's reserved for you. This is no different. The solution is for them (or someone else) to change so as not to use the reserved words. Of course they're gone ahead and written the app, finished it, want to get payment and dont really want to go back and have to re-write the job and test it all over again. SO they'll be trying every which way to get out of it. Fair enough, I can understand it, and whether or not they can be required to do it will depend to some extent on what the terms of their engagement were in the first place. Just my thoughts on it. I think you're quite right. Oh, and I only ever used Access once for a web site That was enough to convince me. I have a client who uses Access too - resists all attempts to get her to change because she wants to do her updates on her PC as she's on the road and then upload the modified database to her site periodically. And it gives NO END of hassles. Still it's her site, she wrote it and maintains it, you can give advice but you can't force clients to follow it. Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 1/9/07, Stephens, Larry V <[EMAIL PROTECTED]> wrote: > > An organization I work with recently hired a firm to redo their website. > This includes both HTML and CF. > > A problem cropped up on a portion of the work. I looked at their code > and found they were using reserved words for field names, e.g. Year. > > The query worked when I pulled it out and plugged it into MS Access > (2003) but choked when ran through CF7 running on a new webserver > running Windows 2003. I changed the field name to an unreserved word > (and futzed through their code making corrections) and we hopped right > past the previous chokepoint until it hit another reserved word they had > used. > > In going back to them they continually ignore us about using reserved > words and keep looking for other solutions. They asked us to change the > CF administrator from Access with unicode to just plain Access and now > it seems to work (although there are other problems cropping up). > > My question: isn't their approach just applying a bandaid to the wound? > My recommendation is to make them toe the line and redo the code (and > tables) so reserved words are not improperly used. > > > Larry V. Stephens > Indiana University > Office of Risk Management > [EMAIL PROTECTED] > 812-855-9758 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:265957 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
