--- In firebird-support@yahoogroups.com, "Jules" <julesp@...> wrote:

>
> Hey,
>
> I have a test system running fb1.5.
>
> I am in the process of testing my 1.5 installation as we are moving

from fb 1.02

>
> I have been using the USER keyword in my fb1.02 db for years to

validate users. But now find the exact same scripts do not work in
fb1.5.

Is that a co-incidence though?

Here is a test case to prove USER works in FB 1.5

CREATE PROCEDURE SP_TEST
RETURNS
(
BLAH VARCHAR(30)
)
AS
BEGIN
BLAH = USER;
SUSPEND;
END
^

COMMIT;

SELECT * FROM SP_TEST;

BLAH
=======
SYSDBA

>
> I was successful in importing the isc4.gdb to the new security.fdb

and can view the users in both the o/s and using ibexpert.

>
> The error I am getting is
>
> "The cursor identified in the update or delete statement is not

positioned on a row. no current record for fetch operation"

>
> Can anyone offer a suggestion?

Not without seeing any code. Some ambiguouity rules have been
enhanced in FB 1.5 which may mean that some queries that would have
been accepted are now rejected because they are not clear as to what
you were asking. For example, if you join two tables and then put
your where clause as 'where ID=1' and both tables have an ID field,
this is ambiguous.

Adam