Hello,

I want to use the TTable in a (self made) object, and I don't want to use a
TTable I placed on my form. In my object, I can use it as Form1.TTable, but
in this manner is a form neccesery.

When I declare Table as TTable in my object, I get runtime errormessages.

Sorry for my english,

This generates an 'access violation':

function
TSAPI.GetTableFieldRights(TableName:string;Field:string;User:string):integer
;
var Table:TTable;
    index,Rights:integer;
    SecData:TSecData;
begin
   Table.NewInstance;
   Table.DatabaseName:='TDM';
   Table.TableName:=Tablename;
end;

Marinus den Breejen <marin...@harley.nl> wrote in article
<01bd41ce$afa90500$05000...@bohr.harley.nl>...

Try (top of my head, don't shoot ;-):

  Var table: TTable;
  Begin
    table := TTable.Create( Application );
    table.DatabaseName:='TDM';
    table.TableName:=Tablename;
    { set various other props }
    table.Open;
    { blah blah }
    table.Free;
  End;

JdV!!

  First, don't EVER name a component after it's parent type...  (ie. naming
a TTable as Table, TOpenDialog as OpenDialog (etc...)  --  Give them usuable
names (MyTable or Table1, etc...)

  Now, why in the world are you creating a TTable at run-time?  (Because you
don't want it on your form?  --  Then use a datamodule...)  --  Doing what
you're doing is (i'm sorry, no offense) stupid...  You're going to have to
programatically go through and hook up all your components, datasources,
everything...  It's a COMPLETE waste of time, when all you have to do is do
it at run-time...  Like I said, there's absolutely no reason to do this
(hell, put the left and top property at 5000, so you'll never see it...)

  However, if you're that deteremined to do it, good luck...  You're going
to need it...

--
Jason Wallace
SL Software
Dark...@SLSoftware.reno.nv.us
--
"We are Microsoft.  Resistance is Futile.  You will be Assimiliated."

  It's also because of the variable...  Never name a component after it's
parent type --  This will GPF your app. faster then you can shake a stick at
it...

--
Jason Wallace
SL Software
Dark...@SLSoftware.reno.nv.us
--
"We are Microsoft.  Resistance is Futile.  You will be Assimiliated."

No offence Jason, but I don't think it's stupid at all.  I quite often
instantiate a TTable to perform a lookup (e.g. I have a function which
instantiates a TTable to return unique keys from my Unique Key table).
TTables I use like this are never connected to any datasources or
data-aware components, so that isn't a problem.  It also means I can use
TTables in units which don't have associated DFMs (the original poster
never said he had a form...), which keeps my project simpler.  Also the
original poster didn't say which version of Delphi he was using; i.e. if
he's using Delphi 1, a datamodule isn't an option.

Also forgive me if I'm wrong, but surely "Table1" is as differently named
from TTable as "Table", from the compilers point of view?  Having said
that, I use Hungarian notation when naming components...

I don't think luck comes into it.  As a developer, I'm quite capable of
tidily doing exactly what the original poster wants.

Regards,

--
Conor
   (conor at crannburn dot com
    Remove garbage from email address to activate)

Jason Wallace <Dark...@SLSoftware.reno.nv.us> wrote in article
<6d1ik8$9s...@news.greatbasin.net>...

Hi Jason,

Jason Wallace <Dark...@SLSoftware.reno.nv.us> wrote in article
<6d59kp$ot...@news.greatbasin.net>...

The original poster said:

Cheers,