James Revillini

Say 'no' to styrofoam.

Tag: bugs

Resolve sudden #Name? output in detail section of Access 2007 Report

I had a working report in Access 2007. It sourced a query called Rosters. The report grouped by several course-related fields, and then in the detail section, it printed names and student IDs. The effect was a stack of printable student rosters.

Then I needed to change the Rosters query to do a little filtering. I did that, saved it, and ran the report again. Suddenly, all the student details were outputting “#Name?”

The usual culprit is changing the names of fields in the query, but that was not the problem this time. The report has simply gotten disconnected from its data source in ONLY the details section. That’s what made it so weird.

The resolution was to click the “Add Existing Fields” in the menu, then drag in one of those fields to the details section, then save, then run the report, then get rid of the extraneous field. From then on, it preserved the connection.

IE6: The goddamn hidden cache

Aside from the ‘goddamn’, this article title may sound like a good movie name.  Anyway, it turns out that IE has a hidden cache of temporary internet files (TIFs).  Big deal, right?  Everyone and their grandmother knows that Windows/IE/MS-products-in-general and even software-in-general have these caches of files for whatever reason – sometimes good, sometimes not so good.  A little Google searching and you find out how to unhide your hidden and system files and hot dog – you can see everything.

Wrong. Despite doing everything the Windows UI allows you to do to see ‘hidden’ files, there is a folder called Content.IE5 which you will not find. It can be reached by a few different methods, but the most direct is: Start > Run > “%homepath%\Local Settings\Temporary Internet Files\Content.IE5”.  There you may find some 8-character long folders, an index.dat file, and maybe a desktop.ini file.  Browsing these folders and/or deleting the contents may be nigh impossible, especially if you’ve ever had a cache overflow problem, and especially if you’ve ever had a browser hijacker which sat there reloading incomplete web pages over and over.  Such was my case.  A colleague has entrusted me to clean up some problems on her computer, and this goddamn cache is preventing me from moving forward*.  There are probably 10s if not 100s of millions of little files in these folders.  I’m currently running CClean on it.  It seems to be the only thing that can knock them out at a decent pace.  Even a command line del command just hung.  Shift+Delete? Forget about it.

This issue is confounding, it’s bullshit, and from what I’ve read, it’s still a problem in the latest incarnations of the ghost of Windows past.  Thank god for browser choices such as Safari, Firefox, and Chrome.  To me, junk like this defeats every other MS zealot’s argument in favor of using the ‘standard’ browser, Internet Explorer, or as I prefer: Internet Destroyer.

*a thorough virus scan on a computer takes a long time.  Uselessly scanning millions of tiny files which are garbage data can take all night + all day + ??? I couldn’t let it continue. 24 hours later and it was still scanning in the same folder which I didn’t even care about!!!

Kill Dreamweaver (works every time!)

Weirdest thing: if you create a stylesheet that is linked to from one of your pages in dreamweaver and it contains the line

.popup {}

int it, dW dies while trying to start up.  Great parlour trick!

Possible bug in Error Tracker Pepper for Mint Statistics

I think I found a bug in Error Tracker 1.06, a plugin for Mint.  I came across this one because even though I had taken measures to redirect a certain incorrect URL that was apparently getting a lot of hits, the hit count on that URL continued to climb.  I ran my own queries against the database to confirm my suspicion that the numbers were wrong.

My findings and solution are found in comments 17, 18, and 19 on the Error Tracker page at XHTMLed.com.

Mango Bugs

Here’s the current bug list for Mango that I’ll be working on over the next week or two. After this list is complete, the initial release will go online. Nightly backups of data will be required just in case I miss something which causes the database to become corrupted.

double what do i do? fixed
auto focus fixed
registration is stupid if it works fixed
after reg, auto login the user fixed

pressing enter is no work in form fixed
show me that i logged in fixed

show me that i logged out fixed

New Document link should be removed
feature request: search next version
powered by link goes nowhere

add spacing to title fixed

edit page
upload ten files, click save. expectation: files are added to revision. actually: files are saved to document, must be manually attached to revision. fixed
manually attaching files doesn’t seem to work fixed

all pages
it would be nice to allow chronological sorting as well next version

seek an anchor based on action (index/add/view) next version
pages that need help fixed

  • all pages
  • become an author

redirect this page to the edit page. who the hell needs to see this? move the updated and joined dates over to the edit page as information. fixed

edit profile
remove roles from page if not admin fixed
double what do i do fixed
Submit button should say “Save” fixed
save should save, then go back to editing page with a message that things were saved fixed
feature request: add button for “pages i’ve edited” next version

lock down to admin permissions fixed

new document
creating a new page (at least by going to the url) doesn’t seem to work fixed

‘no element found’ in firebug or firefox javascript console (part 2)

I was right. If the server sends a response and the ‘Content-Type’ attribute is ‘text/xml’, you must send at least a root node so the xml parser that is built into Mozilla’s XMLHTTPRequest object doesn’t cak and give you a ‘no element found’ Javascript error.

This could be an issue for those of us who are trying to do the REST thing and send back proper status codes depending on the request method and actions taken by the server. A 204 (Updated) or 205 (Deleted) response cannot, by definition, have any content body, so sending a root node is not an option to get around this error. The server needs to determine if the response is going to have an xml content body and assign the Content-Type on the fly.

‘no element found’ in firebug or firefox javascript console

I think I figured it out. I think that the issue crops up if your server sends a response header of ‘Content-Type’ set to ‘text/xml’ and you send no content. The XMLHTTPRequest object then says ‘oh it’s xml? fine – i’ll just PARSE THIS and store it in the reponseXML property.’ At that point, the XML Parser probably bombs and nothing catches it. But anyway that’s just a hunch and I’m only blogging about it because I’m bored. I’ll have test results available later.

A Bug in FireBug

Firebug 0.4.1 and 0.4.0 suffer from a very peculiar bug. If you create an object with a property called ‘-URL’, you can not use console.log to see the value of the property using the console.

Steps to reproduce:

In the console, type

x = {'-URL' : 'foo.pdf', '-Size' : 100};

Now type


Now press enter and click on the [Object object] item which shows up in the console. You will see the ‘-Size’ property, but not the ‘-URL’ property. Next, enter the following into the console and press Enter:


You should now see “foo.pdf” get output to the console. So the value is in Javascript memory, but Firebug won’t show it to you. On a related note, you also cannot view methods of a custom object which are defined using the same means as described above … most of the time. Sometimes it works, so I can’t say for sure what the steps are to reproduce this behavior every time. Why am I blogging about this? Hopefully it will save some other Javascript developer a few hours. Credit goes to my friend, Matthew Metnetsky, for showing me the issue.

© 2017 James Revillini

Theme by Anders NorenUp ↑