Re: HELP!!! - Urgent assistance is needed

I FOUND IT !!!!!!!!!

During an installation of another program - apparently also developed by
Borland, (a very early version) - the DLL-file "MIDAS.DLL" (on my PC
originally dated 2005) was overwritten by a MIDAS.DLL from 2000

Puhhhh

Anders

"Anders Balslev" <itq@xxxxxxxxxxxxxxxx> wrote in message
news:4756f1a6@xxxxxxxxxxxxxxxxxxxxxxxxx
Anything news?

I have made following test:

Created a new SQL database, containint table0 (=Master), Table1, Table2
...Table15 as the only objects

Same problem

Changed the keyfield from UNIQUEIDENTIFIER into INT(Identity)

Same problem

Created a MSAccess database, containng Table0(=Master), Table1, Table2
..Table15

Same problem

Used Delphi 6 (My previous version)

Same problem

Installed temporarily Delphi6 on another PC, and made the same things

NO PROBLEMS

I do not use BDE engine, but ADO.
However - has BDE any kind of influence ? (On the problem PC, the BDE
Engine has been reconfiguret in order to run another programme)

Any advise if highly appreciated

Anders

"Anders Balslev" <itq@xxxxxxxxxxxxxxxx> wrote in message
news:4756941c@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi

BDS 2006

MSSQL 2000

I have faced a very strange and unexplainable error.

I do have a MS SQL database, containing a number of interrelated tables.

A Mastertable, and > 15 detail tables.

In my datamodule, I have an ADODataset for each table, and arranged
MasterDetail relations in the datamodule (MasterSource-->MasterFields
etc.).
All my keyfields are 'UniqueIdentifier' type

I have a DatasetProvider pointing on the mastertable, and by adding
fields in the field editor, I see all the fields from the database, and
also the datasetfields (Nested datasets).

Apparently, when I have more than 13 details tables (nested datasets),
and I click on the "add fields" on the editor, (or trying to open the CDS
in designtime, also when no persistant fields are added) I get following
errormessage:
"Operation not applicable"

Regardless which one I remove, I again can add the fields, so I presume
it has something to do with resources.

Of cource, same error comes in runtime by attempting to open the CDS

The ADODatasets can all be opened without problems


I have no idea where to search

Any help will be highly appreciated

Anders







.