Subject Re: The plot thickens. Additional access errors
Author dale tabbert
Hello Helen,

Thank you for your reply.
<HB>
> The "trial components" are the same as the registered version.

It is funny because I uninstalled the release version and reinstalled
the trial version. Now everything works well again.

<HB>
> Delete the schema cache, as a first step. You need to do that each
time
> you change metadata. Having schema caching during development is
thus not
> a good idea.

I was not aware that I had created the/a schema cache. Not wanting
to sound stupid, what is it and how do I delete it.


<HB>
> Do you know about the InterBase bug that requires you to prepare a
stored
> procedure EVERY time you call it?


No I was not aware of this bug. I do however use the prepare
statement. I have a IB_DSQL (the sp only returns one row so I used
this component) with the SQL of
"Select * from ADD_Directory
(:Directory_Type, :Directory_Class, :parent_id,
:supervisor_id, :description, :email, :name)"
The stored procedure returns the ID (integer) of the new object.
This GPF is happening in an ASTA Business Object when I call
ExecSQL. Here is the portion of the code for that ASTA BO:


// Add the directory
with spAddDirectory do begin
prepare;
ParamByName('Directory_Class').value :=
ClientParams.ParamByName('Directory_Class').value;
ParamByName('Directory_Type').value :=
ClientParams.ParamByName('Directory_Type').value;
ParamByName('parent_id').value :=
ClientParams.ParamByName('parent_id').value;
ParamByName('supervisor_id').value :=
ClientParams.ParamByName('supervisor_id').value;
ParamByName('description').value :=
ClientParams.ParamByName('description').value;
ParamByName('email').value :=
ClientParams.ParamByName('email').value;
ParamByName('name').value :=
ClientParams.ParamByName('name').value;
ExecSQL;
Directory_ID := Fieldbyname('Out_Directory_ID').AsInteger;
end;{with spAddDirectory}


Thank you for your time and patience.

Dale