I have used UD4 and now use MX but it is not working properly. When making a results page some of the drag and drops from my recordset onto my page work while others just show up as a ASP yellow shield - surely this is not right- the text does not show up as dynamic text in the recordset, although I am able to preview in IIS? When I try and refine the search by using selected fields etc I get into real problems as MX writes unresolvable queries. Does anyone know how I can get MX to work properly?

Edited by - flc on 12 Mar 2003 00:06:21

Is this happening with all files or only with files that you have created with UD4. Some of the extensions doesn´t work in MX ex. Conditional region extension.

I redid all the pages from scrap using MX as I thought it might have been some sort of translation problem from UD4 so they should be OK. I am going to try reloading the software and see if that helps

To all,

Reading through old forum entries, I stumbled onto this ASP gold shield issue. I have been having the same problem for a long time now. It originated in MX and still exists in MX 2004. I was hopping that the 2004 upgrade would solve the problem. The problem is with your .Net framework. MX and MX 2004 do not have a server side translator for ASP pages that are using the .Net Framework 1.1. I have read about allot of people just uninstalling the 1.1 .Net framework and the issue being resolved, but I have tried that and I still get the little gold shileds. Microsoft then released service pack 2 for the .Net framework 1.1, so I did that. Still no luck. I noticed the late entry on this forum is a few months old now, did either of you resolve the issue in any way, or are you still living with it? I hope you can help. Thanks

Do you know what? - I did eventually sort my problem out.....the glitch was with my naming conventions on my database setup. I used an access database and whilst UD4 didn't seem too picky about naming conventions, DWMX is! Check you have no spaces in either your database name or any of the fields within it - basic stuff I know, but I managed to overlook it.
It threw me 'cos UD4 worked fine...hope this helps you out

flc,

Thank you so much. I've been working on this problem for a few months no, Macromedia is claiming they have no clue as to whats going on, and in the forums at macromedia.com everyone is blaming this on the framework. I will hop over to the macromedia.com forum and let everyone know how easy of a fix this was. Thanks again.

jnet

Whoa- that does make sense, flc. And a very simple fix, too- I generally never include spaces in the names so wouldn't have suspected something so simple (and as you've noted, DW certainly got 'stricter' with such syntactual glitches as it matured and we had to get more compliant). UD was very lax in comparison.

Definitely post this over at the MM forums, too- I wasn't aware anyone was casting blame there, but regardless it's good to hear this got resolved.


- Scott

scott fegette
macromedia, inc.