|
|
|||||||||
|
|||||||||
|
|||||||||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
SlickEdit: Code in over 40 languages across 7 platforms. SlickEdit’s unmatched power, speed, and flexibility allows even the most accomplished developers to write better code faster. Download a free trial today! |
|
#16
|
|||
|
|||
|
Quote:
You already did so I'll move on to something else
__________________
====== Doug G ====== I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain |
|
#17
|
|||
|
|||
|
To elaborate a bit more, nothing I can find in the Access documentation indicates that IIF is a supported Jet SQL statement, rather that it's a VBA function in access. Generally VBA functions in Access are not available to external ADO code, so my guess is still that the OLEDB provider or something else is performing the IIF, giving undesired results.
|
|
#18
|
||||
|
||||
|
just got very interesting results.
I have executed the code in post #7 on my local machine and got no "extra" contents, it only truncated the string after 255 characters. I have changed the code back to this: Code:
sql = "SELECT id, name, section1, " &_ "IIF(section1_enabled, section1, 'Empty') as sect1 " &_ "FROM pages WHERE name = '" & page & "'" attached is the result as IIF_screenshot_2.GIF. after this I created system DSN and changed the code to use this DSN.. I got error: Code:
Microsoft VBScript runtime (0x800A000D) Type mismatch: 'Server.HTMLEncode' to fix that, I changed this line: Code:
section1_HTML = Server.HTMLEncode(rs("section1"))
to this: Code:
section1_HTML = Server.HTMLEncode(section1) and guess what? I could not replicate the problem of getting "trash" contents. it always returned the first 255 characters of whatever I gave it. |
![]() |
| Viewing: ASP Free Forums > System Administration > Windows Security > Access IIF security leak |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|
|