このページは既にアーカイブ化され、その後の更新はありません。

この商品を購入するには、http://www.rainier.co.uk/products.htmに移動してください。

ExcelController

Integrate your applications with multiple versions of Microsoft Excel.

Jumar Solutions 社の製品

ExcelController のレピュー

平均レビュースコア: 5 (3)

5 つ星中 5

5 つ星
100%
4 つ星
0%
3 つ星
0%
2 つ星
0%
1 つ星
0%

最も最近のポジティブなレビュー

Paul Corr USA5 つ星
Excellent product, I would highly recommend it to anyone who is looking to lightly integrate Excel into their application but does not want to spend the time understanding the Excel object model... 続きを読む

最も最近の重要なレビュー

この商品の否定的なレビューはありません。
Paul Corr ご購入済みのお客様USA5 つ星
Excellent product, I would highly recommend it to anyone who is looking to lightly integrate Excel into their application but does not want to spend the time understanding the Excel object model (although you still have access to it, if you want). I am using Excel to provide flexibility to my end-users in defining their own templates for reporting purposes, and have found the product works very well in this role. It's transparent handling of various flavors of Excel were the prime motivator (I cannot control what version my end-users will use), which was one of my major concerns, having dealt with this issue in prior applications. My application is written entirely in C++, so I don't have the benefit of Visual Basic's dynamic encapsulation of object methods and prperties, so this product provided a nice level of insulation. I hope to send off to them a more C++ friendly class I've written to wrap the COleDispatchDriver-derived class built by the Visual C++ wizard. Certainly not required, but helps reduce some of the overhead associated with *any* VC++ ActiveX interface (no fault of theirs). It's certainly worth the cost just in terms of time savings, even if you're planning on using some of Excel interfaces directly. I was loading templates, doing search/replaces, and printing in about 30 minutes, and I've already proven it out on threee versions of Excel (2000, XP, 2003). Kudos!
Trevor BradleyUnited Kingdom5 つ星
Accessing Excel from Delphi - a dilemma. We had need for a major rewrite of some existing internal software. To split the workload, and to get the project up and running as quickly as possible, we decided to do all the interface for the project in Delphi and all the calculation ‘donkey work’ in Excel. Well why hardwire all these computations into Delphi when they will be changed quite often, a task to which Excel is well suited? My side of things involved Delphi. So now I had to work out how to get Delphi to load, read and write and close an Excel file that was going to be supplied to me by somebody else. I had two options - write the thing myself or buy in something that did the job for me. So I started to research how to do this myself. I looked at the example Delphi code and realised that to recreate all the Excel functions I needed in Delphi was going to take me forever and a day. This wasn't going to be a simple task. And I have a deadline to complete the whole project. So then I researched what was out there that could save me the time I desperately needed. I started 'Google-ing' for Delphi Components to do this. Yes, there were some out there. But I tried them and wasn't entirely happy each time. Some didn't perform as I wanted, others had very sketchy documentation. And then, purely by accident I have to admit, I came across ExcelController. Now, at first, I was very sceptical. This wasn't a native Delphi component, it was an ActiveX/DLL. I'd had some experience of this route with other libraries such as Acrobat. I downloaded the trial, imported the type library into Delphi and that was it. There it was, everything I needed. The documentation is excellent as either a printable Word document or in the usual Microsoft help format. I tried a few small examples and was very quickly loading, reading and writing to Excel. I then decided to try to 'beat' ExcelController and try accessing Excel with named cell ranges (the method the Excel programmer is using to give me ‘access points’ to his worksheets) and I was delighted to find that it handled everything perfectly. The above involved a little help from Rainier, but they responded quickly to my query that isn’t always the case with other software companies these days. One other company took a week to respond to a query I had while trialing an Excel component, by which time I had already given up and moved onto something else. The trial version has a nag screen but other than that functions exactly like the retail version. But even the nag screen is coded in a manner that it doesn't interfere with development of test projects. It is just displayed at random intervals when any of the ExcelController functions are called. We didn’t take long to decide to purchase the retail version, and, IMHO, it's well worth every penny. My only minor gripe, and it is very minor, is that I have to define all parameters to be passed to ExcelController functions as variables. But this may be caused by the way Delphi handles type libaries rather than ExcelController. If you are looking to interface Delphi and Excel, buy ExcelController. Trevor.
Trevor BradleyUnited Kingdom5 つ星
Accessing Excel from Delphi - a dilemma. We had need for a major rewrite of some existing internal software. To split the workload, and to get the project up and running as quickly as possible, we decided to do all the interface for the project in Delphi and all the calculation ‘donkey work’ in Excel. Well why hardwire all these computations into Delphi when they will be changed quite often, a task to which Excel is well suited? My side of things involved Delphi. So now I had to work out how to get Delphi to load, read and write and close an Excel file that was going to be supplied to me by somebody else. I had two options - write the thing myself or buy in something that did the job for me. So I started to research how to do this myself. I looked at the example Delphi code and realised that to recreate all the Excel functions I needed in Delphi was going to take me forever and a day. This wasn't going to be a simple task. And I have a deadline to complete the whole project. So then I researched what was out there that could save me the time I desperately needed. I started 'Google-ing' for Delphi Components to do this. Yes, there were some out there. But I tried them and wasn't entirely happy each time. Some didn't perform as I wanted, others had very sketchy documentation. And then, purely by accident I have to admit, I came across ExcelController. Now, at first, I was very sceptical. This wasn't a native Delphi component, it was an ActiveX/DLL. I'd had some experience of this route with other libraries such as Acrobat. I downloaded the trial, imported the type library into Delphi and that was it. There it was, everything I needed. The documentation is excellent as either a printable Word document or in the usual Microsoft help format. I tried a few small examples and was very quickly loading, reading and writing to Excel. I then decided to try to 'beat' ExcelController and try accessing Excel with named cell ranges (the method the Excel programmer is using to give me ‘access points’ to his worksheets) and I was delighted to find that it handled everything perfectly. The above involved a little help from Rainier, but they responded quickly to my query that isn’t always the case with other software companies these days. One other company took a week to respond to a query I had while trialing an Excel component, by which time I had already given up and moved onto something else. The trial version has a nag screen but other than that functions exactly like the retail version. But even the nag screen is coded in a manner that it doesn't interfere with development of test projects. It is just displayed at random intervals when any of the ExcelController functions are called. We didn’t take long to decide to purchase the retail version, and, IMHO, it's well worth every penny. My only minor gripe, and it is very minor, is that I have to define all parameters to be passed to ExcelController functions as variables. But this may be caused by the way Delphi handles type libaries rather than ExcelController. If you are looking to interface Delphi and Excel, buy ExcelController. Trevor.