B
Badger
Hey,
I've an automated report generation application built using word,
excel and sql server. Essentially, it uses MS Word as a WYSIWYG
editor, with excel underneath it formatting charts and tables and the
data is sourced from SQL Server.
The problem is that on one PC in the office, the process falls over.
It always falls over at the same point in the excel application,
however, if i run the routine directly in excel (i.e. not from word
via the automation server) it works fine. It throws a vba error then
excel crashes and closes. The error is due to an ado recordset not
being populated - although there's nothing wrong with the query. It
works fine on all other PCs in the office.
I'm trying to nail it down to something less dramatic than
reinstalling word / excel. I've had a similar scenario many years ago
writing a massive Word template application. Every now and then a
registry key would become corrupt and need recreating. Unfortunately
that was six years ago and i've no idea what the key was!
I've tried recreating normal.dot, that didn't cut it.
Anyone seen anything similar / got any suggestions?
The application flow roughly runs:
1. user runs up a new word document from a template
2. gets presented with a form, enters some parameters and hits go.
3. Word creates an instance of excel, opens a new excel workbook based
on a template
4. Executes a procedure in the excel workbook which creates a
connection to sql server and carries out various bits of data access.
5. The results of that data access are applied to the tables and
charts in excel.
6. Word grabs the updated content it needs from excel.
7. Cleans up connections and closes excel.
8. Returns control to the user.
I've an automated report generation application built using word,
excel and sql server. Essentially, it uses MS Word as a WYSIWYG
editor, with excel underneath it formatting charts and tables and the
data is sourced from SQL Server.
The problem is that on one PC in the office, the process falls over.
It always falls over at the same point in the excel application,
however, if i run the routine directly in excel (i.e. not from word
via the automation server) it works fine. It throws a vba error then
excel crashes and closes. The error is due to an ado recordset not
being populated - although there's nothing wrong with the query. It
works fine on all other PCs in the office.
I'm trying to nail it down to something less dramatic than
reinstalling word / excel. I've had a similar scenario many years ago
writing a massive Word template application. Every now and then a
registry key would become corrupt and need recreating. Unfortunately
that was six years ago and i've no idea what the key was!
I've tried recreating normal.dot, that didn't cut it.
Anyone seen anything similar / got any suggestions?
The application flow roughly runs:
1. user runs up a new word document from a template
2. gets presented with a form, enters some parameters and hits go.
3. Word creates an instance of excel, opens a new excel workbook based
on a template
4. Executes a procedure in the excel workbook which creates a
connection to sql server and carries out various bits of data access.
5. The results of that data access are applied to the tables and
charts in excel.
6. Word grabs the updated content it needs from excel.
7. Cleans up connections and closes excel.
8. Returns control to the user.
