Definitely go for the code, not embedding.

Post #361,980 by malraux 8/23/12 10:42:51 PM Reply	Definitely go for the code, not embedding. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #361,988 by crazy 8/24/12 1:35:02 PM Reply	That's what I decided a month ago Then the CTO flipped out over my decision to put the customer database on the webserver. Sigh. More political than anything else. He wanted to assert some authority over me. I invited him to cancel the project and do a full redesign, since I can't fix him and can't drag him to a psychiatrist. Owner got involved, we did a design review, everyone decided my method made sense and they were ok with it. Twitch twitch twictch.
Post #361,995 by static 8/24/12 7:14:21 PM Reply	I was busy so I didn't answer before. But I agree. Your approach is the accepted best practice. Wade. Just Add Story http://justaddstory.wordpress.com/
Post #361,999 by drook 8/25/12 9:40:38 AM Reply	Another answer late to the party What problem are you trying to solve? Does each customer get custom pricing? A different list of seminars to select from? What customization do you NEED on the web order form? Have you considered just putting the forms up with ugly generated URLs and assume that anyone who shows up must have received an offer? If the pricing etc is different do the same thing but pre-generate ALL the pages with the customization already built in. That has the risk that someone will forward their e-mail to someone else, so you'd have to decide if you have the kind of customers who would do that. -- Drew
Post #362,010 by crazy 8/26/12 6:59:52 AM Reply	Hmm Don't care about most of that. Same prices, same calendars. We simply want a bit of control over competitors who would scrape our site for customers.
Post #362,012 by drook 8/26/12 11:47:55 AM Reply	Then generated, expiring URLs might be all you need -- Drew

Welcome to IWETHEY!