商品説明の翻訳が完了していない商品については、Google翻訳サービスへのリンクを表示しております。 ただし機械による自動翻訳は必ずしも翻訳結果が正確ではないことにご注意願います。

Powered by

ComponentOne Studio Enterprise Doc Edition(英語版)

.NET および、ASP.NET 、 Mobile Device 、ActiveX 対応のアプリケーションに、グリッドや、レポート、チャート、データ操作、ユーザーインターフェイス機能を追加。

GrapeCity 社の製品
1996 年より日本国内にてComponentSourceで販売中。

レビューの平均スコア: 3.50レビューの平均スコア: 3.50レビューの平均スコア: 3.50レビューの平均スコア: 3.50レビューの平均スコア: 3.50 (6)

i

Component One Studio Enterprise Doc Edition is no longer available to purchase as a standalone product, you should purchase ComponentOne Ultimate instead. If you are looking to renew your subscription then you should purchase the renewal for ComponentOne Ultimate which includes even more products for the same renewal fee as Component One Studio Enterprise Doc Edition.

ComponentOne Studio Enterprise Doc Edition のレピュー

平均レビュースコア: 3.5 (6)

5 つ星中 3.5

5 つ星
49%
4 つ星
0%
3 つ星
17%
2 つ星
17%
1 つ星
17%

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

espuaMalaysia5 つ星
My comments on the VS View Classic 8 (ActiveX) This is a satisfying product that has been well designed for Rapid Application Development with a reasonable file size. With this printing component, I... 続きを読む

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

neilNew Zealand1 つ星
I found the ComponentOne TrueData controls too buggy and unreliable. My code was filling up with 'fixes' to work around problems so their controls would work properly. After converting a DAO project... 続きを読む
le_slothUnited Kingdom2 つ星
Our company has been using ComponentOne products for about 7 years now - mostly FlexGrid, vsPrinter and SizerOne (both in ActiveX and more recently the .NET versions). To be honest, they're not as good as they used to be! FlexGrid is definately the best of the lot - I haven't really been able to find anything as good as this for unbound grids (though it could be so much better!). The object model takes some getting used to when making the transition from ActiveX to .NET control, but I suppose it makes more sense (they do actually provide another version called FlexGridClassic, which uses a lot of the older object model, but loses some of the new functionality). SizerOne isn't really needed in the .NET world IMHO - WinForms have everything you need already built-in. vsPrinter has always been a bit of an odd one in ActiveX form, yet to see whether we will need to use this in .NET. OK, so none of this sounds too bad so far...that is until you want any form of Support (wait forever for a response and usually this is either the wrong answer or is far too brief!). Documentation - as with many component companies, this really, really needs improving. Many of the examples don't work, many properties are more or less undocumented and their "HelpCentral" part of their website is worse than useless. ASP.NET controls - why anyone would buy or use these I really don't know! Their own website (which uses these controls extensively) has considerable rendering problems in FireFox - hardly a good example! In summary, ComponentOne need to improve a lot of things in their product suite - my personal feeling is that they have far too many components and products now - there's little point having the biggest suite out there when quality suffers so much across the board. In future we will be looking elsewhere.
espuaMalaysia5 つ星
My comments on the VS View Classic 8 (ActiveX) This is a satisfying product that has been well designed for Rapid Application Development with a reasonable file size. With this printing component, I managed to generate impressive reports (with pictures, layout, header/footer, preview, page setup, tables and etc) on the fly with the very minimum of coding efforts. All the print out can be easily export to RTF, PDF (this saves money for my users on Acrobat) and HTML very easily. Documentation & sample codes has been comprehensive enough and very easy to follow. Though to perform the table formatting during the runtime is a bit tedious, but it is not difficult. I have not tried its features on database reports. However, if you are looking for an easy printing component with good features, VS View 8 certainly is a good choice. Highly recommended.
neilNew Zealand1 つ星
I found the ComponentOne TrueData controls too buggy and unreliable. My code was filling up with 'fixes' to work around problems so their controls would work properly. After converting a DAO project to ADO, I found the ADO versions of the controls crashing all over the place. Maybe it was my computer, but I suspect not. No other controls that I use cause ADO crashes. Anyway, that was as much as I was prepared to put up with, so I dumped TrueData and I'm now using Janus GridEx for grids, plus went back to intrinsic dropdown controls. I haven't had any more ADO problems. My code is signficantly smaller, I've been able to add more features due to better interaction with the control (including sub-classing) and I've found GridEx to be extremely reliable, despite it not having had any updates for a while. TrueData would be good if it was reliable, but despite lots of fixes, I've not seen any improvements. Please note that ComponentOne VSFlexGrid does NOT suffer from these problems and is a good, reliable control. If you want a nice, easy to use grid, although not with all the binding methods of TrueData, then try Janus GridEx. I haven't found a good multi-column combo to replace TrueDBCombo (which I liked, except for it's reliability), so I built one using GridEx.
virtualswpUSA3 つ星
Component One has a wide range of tools that a lot of other control suites don't have. They were the first on the scene with the mobile controls for the .NET compact framework. We continue to use their controls in more and more applications. We have had about 3 or 4 bug submissions and they have all been corrected. A criticism is that a lot of times I am doing the debugging for them though to correct the bugs. Once bugs are submitted they either find a work around or give you a way to download a fixed version within a few weeks. Going forward I would like to see that Component One continue to release and work on controls that are unique. Another thing I would like to see is if Component One improved their overall appearance of the controls to fit Windows XP themes.
PeterNew Zealand5 つ星
As a leader of a development team writing highly visible, business critical software in the global market, I have found our choice to use components from ComponentOne Studio Enterprise successful and rewarding. Our users expect a high degree of professionalism in their software and need any issues resolved in a timely manner. This means that we absolutely must be able to depend on your third party suppliers for their support and cooperation. In the real world, you can never find third party software that completely meets and is 100% free of issues. The large selection of components within the product has given us (a) a wide selection of components to meet the various needs, (b) a single stop shop for support and (c) enabled us to lower our TCO by purchasing from a single vendor. The few issues we have found in using the applications were dealt with a friendly and professional manner. We were able to build a good relationship with the support personnel that enabled us to adequately describe the problem, duplicate the issue within their support environment, and see the required modifications scheduled into their development pipeline. From my perspective you need to seriously considered ComponentOne Studio Enterprise if you are deciding on third party components. Peter
james.pearsonUnited Kingdom5 つ星
I would recommend the VSFlexGrid anytime, but SizerOne, VSPrinter, VSReports etc are limited in functionality and VERY poorly documented. I have tried to build apps using these, but due to the limited functionality, I had to resort to other methods than VSPrinter, SizerOne and VSReports. The help file for VSFlexGrid is not up to Microsoft standards, but adequate for most purposes. If you want an excel look for you data entry app then VSFlexGrid will probably not have enough features to get the look you want; eg/ inability to format individual cells (other than by using VB functions) rather than applying a custom format to whole rows or whole columns. Overall, not bad, but could do with beefing up the help files and providing more code examples.