This is more of a career question for general advice on Excel Object Model Programming.
Not that I have been looking for it, I have not seen .NET applications that utilize Excel Object Model Programming.
Is this a niche' market? Would it be something worth pursuing? Does Mr Excel have training for it?
Back in '97, I was a Microsoft Certified Trainer with certifications from WOSA, VB, Access vba, SQL Server, and Excel Object Model Programming.
I have made a living providing MS Access over Citrix with SQL Server back-end for key workers that typically need under 200 concurrent sessions.
The Access Reports have not been used.
Instead, my speciality is to create unique Business Rules on the SQL Server side that provide metadata along with actual data.
These are presented in highly custom "Excel Reports" often used by business manager as a type of data mining or work-flow management.
The VBA is a great language to perform remote automation from MS Access that links with DSN-Less connections to SQL Server.
But, times are changing. I am looking at learning .NET being used to create the same kind of "Excel Reports"
My understanding is that .NET can reference the Excel Object Model and create the XLSX file.
I would assume the .NET could be compiled as a stand alone executable so the "Excel Reports" could be tied to databases and used on various web services.
Learning the entire .NET Framework for all situations would appear to be a daunting task.
Just wondering if anyone has experience in learning enough .NET programming to create Excel XLSX documents with very rich features?
Is there a market for this? What would the learning curve be for someone well experienced with the Excel Object Model?
Not that I have been looking for it, I have not seen .NET applications that utilize Excel Object Model Programming.
Is this a niche' market? Would it be something worth pursuing? Does Mr Excel have training for it?
Back in '97, I was a Microsoft Certified Trainer with certifications from WOSA, VB, Access vba, SQL Server, and Excel Object Model Programming.
I have made a living providing MS Access over Citrix with SQL Server back-end for key workers that typically need under 200 concurrent sessions.
The Access Reports have not been used.
Instead, my speciality is to create unique Business Rules on the SQL Server side that provide metadata along with actual data.
These are presented in highly custom "Excel Reports" often used by business manager as a type of data mining or work-flow management.
The VBA is a great language to perform remote automation from MS Access that links with DSN-Less connections to SQL Server.
But, times are changing. I am looking at learning .NET being used to create the same kind of "Excel Reports"
My understanding is that .NET can reference the Excel Object Model and create the XLSX file.
I would assume the .NET could be compiled as a stand alone executable so the "Excel Reports" could be tied to databases and used on various web services.
Learning the entire .NET Framework for all situations would appear to be a daunting task.
Just wondering if anyone has experience in learning enough .NET programming to create Excel XLSX documents with very rich features?
Is there a market for this? What would the learning curve be for someone well experienced with the Excel Object Model?
