为啥出现activex Components can't create object?

maliguo_net 2003-10-09 09:21:28
开发环境:
evb,adoce3.1 sql server ce 2.0
背景
已经将程序打包,并且已经将adoce,sql server ce 的相关类库加入到包中
在pda 机器上成功安装
程序说明:
该程序主要是对sql server ce 的操作,增加,修改,删除 纪录
问题:
当连接数据库是,出现activex Components can't create object?
备注:
程序在模拟器运行正常

各位帮忙看看
...全文
84 2 打赏 收藏 转发到动态 举报
写回复
用AI写文章
2 条回复
切换为时间正序
请发表友善的回复…
发表回复
maliguo_net 2003-10-09
  • 打赏
  • 举报
回复
没有,安装时,系统应该自注册了
如何注册?
aawolf 2003-10-09
  • 打赏
  • 举报
回复
是否在实际设备上注册了ADOCE和SSCE的DLL?
Enhance Your Delphi Application with Drop-in Shell Functionality •Includes 18 visual and non-visual componentsCreate Explorer-like applications within minutes with JamShellTree, the JamShellList and the JamShellCombo •Easy drop-in: Just drop the UI components right on your own forms or dialogs •Use checkboxes with JamShellTree, JamShellList, JamFileList and JamDriveList Icons and thumbnails are queried in background threads. This optimizes the reactivity and does not slow down the speed of the user interface. Look-and-Feel of the Windows Explorer •Windows Shell context menu (can be extended with a Delphi popmenu) •OLE drag-and-drop with the Windows Explorer and similar applications •Different view styles: The JamShellList and the JamFileList support small icons, large icons, extra large icons, details mode and thumbnails •Overlay icons supported •Installed Shell extensions, which are supported by the Windows Explorer, are also supported by the ShellBrowser Delphi Edition •TJamSystemShellView instances the right pane of the real Windows Explorer •Background context menu in the JamShelllist is supported How-to Guides •Comprehensive documentation of the included controls •Several sample projects for basic and advanced features of ShellBrowser Delphi Edition included Transparent Costs •The ShellBrowser Delphi Edition is royalty free and involves no runtime fees 100% Delphi Code•The controls are based on the Delphi VCL and are written in 100% Object Pascal code •No additional DLLs or ActiveX controls are necessary
最新版的MDAC(Microsoft Data Access Components)下载。 ========================================== Microsoft Data Access Components (MDAC) Purpose The Microsoft Data Access Components (MDAC) SDK documents the key technologies that enable Universal Data Access, Microsoft's strategy for providing access to information across the enterprise. Microsoft Data Access Components include ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC). Data-driven client/server applications deployed over the Web or a LAN can use these components to easily integrate information from a variety of sources, both relational (SQL) and nonrelational. If you have questions or need detailed information about properly redistributing MDAC, see Redistributing MDAC for a description of the distribution requirements for MDAC. ActiveX Data Objects (ADO) Microsoft ActiveX Data Objects (ADO) provides consistent, high-performance access to data and supports a variety of development needs, including the creation of front-end database clients and middle-tier business objects that use applications, tools, languages, or Internet browsers. The primary benefits of ADO are ease of use, high speed, low memory overhead, and a small disk footprint. ADO provides an easy-to-use interface to OLE DB, which provides the underlying access to data. It uses a familiar metaphor—the COM Automation interface—available from all leading Rapid Application Development (RAD) tools, database tools, and languages. OLE DB Microsoft OLE DB is a set of interfaces that expose data from a variety of relational and nonrelational sources by using the Component Object Model (COM). OLE DB interfaces provide applications with uniform access to data stored in diverse information sources. These interfaces support the amount of DBMS functionality appropriate to the data store, enabling the data store to share its data. OLE DB comprises a programmatic model consisting of data providers, which contain and expose data; data consumers, which use data; and service components, which process and transport data (such as query processors and cursor engines). In addition, OLE DB includes a bridge to ODBC to enable continued support for the broad range of ODBC relational database drivers. Open Database Connectivity (ODBC) The Microsoft Open Database Connectivity (ODBC) interface makes it possible for applications to access data from a variety of DBMSs. ODBC permits maximum interoperability—an application can access data in diverse DBMSs through a single interface. Furthermore, that application will be independent of any DBMS from which it accesses data. Users of the application can add software components called drivers, which create an interface between an application and a specific DBMS. Components of the MDAC SDK Microsoft ActiveX Data Objects (ADO) This section contains Programmer's References for ADO, ADOX, ADO MD, and RDS, as well as samples documentation. Microsoft OLE DB This section documents the OLE DB and OLE DB for OLAP interfaces, including a Programmer's Reference, documentation for various OLE DB providers, and samples. Microsoft Open Database Connectivity (ODBC) This section documents the ODBC interface, including a Programmer's Reference, documentation for various ODBC drivers, and samples.
Version 1.7 ----------- - ADD: Delphi/CBuilder 10.2 Tokyo now supported. - ADD: Delphi/CBuilder 10.1 Berlin now supported. - ADD: Delphi/CBuilder 10 Seattle now supported. - ADD: Delphi/CBuilder XE8 now supported. - ADD: Delphi/CBuilder XE7 now supported. - ADD: Delphi/CBuilder XE6 now supported. - ADD: Delphi/CBuilder XE5 now supported. - ADD: Delphi/CBuilder XE4 now supported. - ADD: Delphi/CBuilder XE3 now supported. - ADD: Delphi/CBuilder XE2 now supported. - ADD: Delphi/CBuilder XE now supported. - ADD: Delphi/CBuilder 2010 now supported. - ADD: Delphi/CBuilder 2009 now supported. - ADD: New demo project FlexCADImport. - FIX: The height of the TFlexRegularPolygon object incorrectly changes with its rotation. - FIX: Added division by zero protect in method TFlexControl.MovePathSegment. - FIX: The background beyond docuemnt wasn't filled when TFlexPanel.DocClipping=True. - FIX: In "Windows ClearType" font rendering mode (OS Windows mode) the "garbage" pixels can appear from the right and from the bottom sides of the painted rectangle of the TFlexText object. - FIX: The result rectangle incorrectly calculated in the TFlexText.GetRefreshRect method. - FIX: Added FPaintCache.rcPaint cleanup in the TFlexPanel.WMPaint method. Now it is possible to define is the drawing take place via WMPaint or via the PaintTo direct call (if rcPaint contain non-empty rectangle then WMPaint in progress). - FIX: The TFlexPanel.FPaintCache field moved in the protected class section. Added rcPaint field in FPaintCache that represents drawing rectangle. - ADD: In the text prcise mode (TFlexText.Precise=True) takes into account the rotation angle (TFlexText.Angle). - FIX: Removed FG_NEWTEXTROTATE directive (the TFlexText Precise mode should be used instead). - FIX: The TFlexRegularPolygon object clones incorrectly drawed in case when TFlexRegularPolygon have alternative brush (gradient, texture). - ADD: Add TFlexPanel.InvalidateControl virtual method which calls from TFle

19,506

社区成员

发帖
与我相关
我的任务
社区描述
硬件/嵌入开发 嵌入开发(WinCE)
社区管理员
  • 嵌入开发(WinCE)社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧