Archive for December, 2005

[FIX] Adobe Reader v.5 fails to open PDF with “There was an error opening this document. A temporary file could not be opened.”

Monday, December 19th, 2005

If you see “There was an error opening this document.  A temporary file could not be opened.” when trying to open a PDF file, you may need to clean out C:\\Documents and Settings\\USERNAME\\Local Settings\\Temp\\Acr*.tmp

Cheers to “gprellwitz” who suggests this here:

http://www.experts-exchange.com/Web/Graphics/Adobe_Acrobat/Q_20790405.html

Jeers to the MSFT developer who decided that “Documents and Settings” with spaces and mixed caps was a better home directory prefix than “home”

[WORKAROUND] “Adobe Reader” version 7.0.5 hangs in Firefox 1.0 and 1.5, using all CPU

Monday, December 19th, 2005

If you run “Adobe Reader” (no longer called Acrobat Reader as of version 6) in Firefox 1.5 (or 1.0) in Windows XP, you may discover that it uses all CPU when opening a PDF doc.

Uninstall Adobe Reader from Control Panel:Add/Remove Programs, and download an old version like version 5 of Acrobat Reader here:

http://www.adobe.com/products/acrobat/readstep2_allversions.html

Thanks to Joshua Burke for suggesting the solution here: http://www.askbobrankin.com/inbox/stumper_firefox_consumes_the_cpu.html

[BUG] ActiveRecord woes with SQL Server odd names (spaces and brackets), ntext data types

Thursday, December 1st, 2005

ActiveRecord (latest versions of ODBC, DBI, and AR as of today
2005-12-01) seems to be having trouble with at least two things that
SQL Server 7 does:

1. The SQL Server adaptor (sqlserver_adaptor.rb) get_table_name sub
expects a name to have no whitespace in it.  The conditional and
regex need to be changed to look for bracketed names like [Poorly
Designed Table].  Then, the columns sub needs to know to take the
brackets off the ends of the names when it looks up the table by its
textual value.  To complicate this, according to
http://msdn2.microsoft.com/en-us/library/ms176027.aspx you can have
either double-quotes or square brackets as your delimiters in SQL
Server names, and you can even escape brackets by doubling.  I
have written hackish code that solves for simple [Dumb Name] tables but
not the whole enchilada, so I’m not posting it here yet.

2. The data type “ntext” seems to create memory allocation problems; I get an error of:

/usr/lib/ruby/site_ruby/1.8/DBD/ODBC/ODBC.rb:220:in `fetch’: failed to allocate memory (NoMemoryError)

Running this on CYGWIN_NT-5.1 RANDALL-VAIO 1.5.19s(0.141/4/2) 20051102 13:29:13 i686 unknown unknown Cygwin on Win XP Pro.