Explorer and MS SQL Server
Hi, we have just purchased Report Builder Enterprise version 6. I have BDE
problems when I try to use the Report Explorer component. I am using MS SQL
Server 2000.
Are there any known problems using MS SQL SErver with Report Builder? and if
not can some one confirm the table structure that is required for the Folder
and Item tables: The ones below seem to cause problems. The Folder creation,
move rename and so on works fine but I can't save a report.
I get EDBEngine Error "BDE Error $000F" when I try to save.
The whole thing works fine when I use an access database, this leads me to
believe I have a problem in MS SQL Server.
Can anyone please help?
Thanks
Paul van Dinther
The table definitions used in MS SQL Server are:
CREATE TABLE [dbo].[ReportFolder] (
[FolderID] [int] IDENTITY (1, 1) NOT NULL ,
[Name] [char] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ParentID] [int] NULL
) ON [PRIMARY]
and
CREATE TABLE [dbo].[Report] (
[ItemID] [int] IDENTITY (1, 1) NOT NULL ,
[Deleted] [datetime] NULL ,
[Name] [char] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ItemType] [int] NOT NULL ,
[Modified] [datetime] NULL ,
[Size] [int] NULL ,
[FolderID] [int] NULL ,
[Template] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
The IDENTITY(1,1) entry provides an auto numbering facility to provide
unique ID's
problems when I try to use the Report Explorer component. I am using MS SQL
Server 2000.
Are there any known problems using MS SQL SErver with Report Builder? and if
not can some one confirm the table structure that is required for the Folder
and Item tables: The ones below seem to cause problems. The Folder creation,
move rename and so on works fine but I can't save a report.
I get EDBEngine Error "BDE Error $000F" when I try to save.
The whole thing works fine when I use an access database, this leads me to
believe I have a problem in MS SQL Server.
Can anyone please help?
Thanks
Paul van Dinther
The table definitions used in MS SQL Server are:
CREATE TABLE [dbo].[ReportFolder] (
[FolderID] [int] IDENTITY (1, 1) NOT NULL ,
[Name] [char] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ParentID] [int] NULL
) ON [PRIMARY]
and
CREATE TABLE [dbo].[Report] (
[ItemID] [int] IDENTITY (1, 1) NOT NULL ,
[Deleted] [datetime] NULL ,
[Name] [char] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ItemType] [int] NOT NULL ,
[Modified] [datetime] NULL ,
[Size] [int] NULL ,
[FolderID] [int] NULL ,
[Template] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
The IDENTITY(1,1) entry provides an auto numbering facility to provide
unique ID's
This discussion has been closed.
Comments
Maybe you are willing to send be the script for the folder and item table.
support SQL2000 or BDE in general does not support SQL2000?
We have many applications accessing SQL2000 through the BDE but have very
few issues with this. With ReportBuilder it is the first time that I have
BDE problems.
Thanks
I suggest that you use ADO for your application rather than BDE if you're
using SQL2000 as a backend database. With ADO there is no need to install
any component since ADO comes with most windows operating system and the
latest office.
This means not having to deal with the BDE installation or config-iing.
With ADO on all W2k machines all you have to do is install MSSQL client. It
is soooo much easier. I ADO believe it is also in 98se.
M$ quit supplying info needed to update the BDE and as I recall did not make
an ODBC driver for SQL2000 either.
M$ says the future is with ADO and so for future compatability ADO, I
beblieve, is the way to go.
area of database connectivity. ADO it is, but... This means many weeks worth
of re-work of existing code. ODBC seems to work fine with SQL2000 but I have
not tested it enough yet.
A big thank you to M$ too (not). I have instructed our sales staff to
immediately stop selling SQL2000 and withdraw outstanding quotes for the
product.
Regards
Paul van Dinther
technology that it use is DAO not ADO. DAO have less futures instead of ADO
which is the actual MS standard.
I use BDE with MS Sql 7.0 and all is OK.
The problem (DBE Error $000F) is from other source. If you search in
Borland News you gonna find a lot of question about this problem. I think
this is a memory problem and you can try to increase the memory amount in
BDE Administrator -> Configuration -> System -> Init (MEMSIZE = xxx).
You can try to not use TTable and use TQuery with CachedUpdates. And for
a better results you can try to use Blobs in detail TQuery ( you can read it
only when you need it).
With ADO you don't need to install anything to the client side (ADO,
like ODBC for SQL Server is allready installed by de SO)
Bogdan Dragulin bobo@ats.minisat.ro