reserved error -1524 access 2007

[Elias Moreno]

I'm using the evaluation version of Office 2007 pro. I have an application
that I was using seamlessly under access 2003 version. When I run it under
access 2007 I find that some queries fail to execute replying the message:

Error reservado (-1524); no hay ningún mensaje para este error.

of course I'm using the spanish version. as a clue, I found in both cases
the error raises in queries with embedded comparison functions (iif).

If somebody can help me I really appreciate.

 

[Allen Browne]

The reserved error means something went wrong that the Access developers did
not anticipate. It is difficult to guess what that might have been.

Not sure what to suggest other than compacting the database:
Office Button | Manage | Compact/Repair

You can try posting the SQL statement here if you wish, but it would be very
difficult to trace what's going on without details of the field types.

If your regional settings are Spanish, I don't know what chararacter you use
as the delimiter. It's defined in the Regional Options of the Windows
Control Panel, and you may need to use that characters in place of the comma
in the IIf() expressions. For example, if you use ; rather than , you might
try:
IIf([A] = ; 1 ; 0)
I've no idea whether that could help.

As always, you want to ensure Name AutoCorrect is turned off:
http://allenbrowne.com/bug-03.html

It might be that JET is getting the data types mixed up. If so, you might be
able to explicitly typecast:
http://allenbrowne.com/ser-45.html

If you have yes/no fields and outer joins, it might be the result of JET's
inability to handle nulls in logical fields
http://allenbrowne.com/bug-14.html

You could try switching the query to SQL View, and copying the statement out
to Notepad. Delete the query. Make a new one, switch to SQL View, and paste
the statement back.

Not sure any of that will help, as I would have expected the same issues
under Access 2003. Perhaps someone else has another idea to contribute as
well.

 

[Elias Moreno]

Allen thnaks a lot for your interest in my problem. Here I add the SQL
statement:

UPDATE EmbarquesPorOT INNER JOIN OT ON EmbarquesPorOT.OT = OT.Cod SET
OT.Surtido = IIf([Uni]="Pz",[Piezas],[Kilos]), OT.PorSuritr =
IIf([Uni]="Pz",[cant]-[piezas],[Cant]-[Kilos]), OT.Estado =
IIf([Uni]="Pz",IIf(([cant]-[piezas])<1,False,True),IIf(([Cant]-[Kilos])<([cant]*0.05),False,True)), OT.MatlEnProceso = False
WHERE (((OT.Estado)=True));

As I had been working on this, I found the if I delete the WHERE statement,
the message dissapears. Anyway, thats useless to the purpose. The headhache
is that, the application is fully functional under MsAccess 2003. The
application is a 2003 mde file, but the linked databases are Access 2000
files. could this be affecting?

The reserved error means something went wrong that the Access developers did
not anticipate. It is difficult to guess what that might have been.

Not sure what to suggest other than compacting the database:
Office Button | Manage | Compact/Repair

You can try posting the SQL statement here if you wish, but it would be very
difficult to trace what's going on without details of the field types.

If your regional settings are Spanish, I don't know what chararacter you use
as the delimiter. It's defined in the Regional Options of the Windows
Control Panel, and you may need to use that characters in place of the comma
in the IIf() expressions. For example, if you use ; rather than , you might
try:
IIf([A] = ; 1 ; 0)
I've no idea whether that could help.

As always, you want to ensure Name AutoCorrect is turned off:
http://allenbrowne.com/bug-03.html

It might be that JET is getting the data types mixed up. If so, you might be
able to explicitly typecast:
http://allenbrowne.com/ser-45.html

If you have yes/no fields and outer joins, it might be the result of JET's
inability to handle nulls in logical fields
http://allenbrowne.com/bug-14.html

You could try switching the query to SQL View, and copying the statement out
to Notepad. Delete the query. Make a new one, switch to SQL View, and paste
the statement back.

Not sure any of that will help, as I would have expected the same issues
under Access 2003. Perhaps someone else has another idea to contribute as
well.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

I'm using the evaluation version of Office 2007 pro. I have an application
that I was using seamlessly under access 2003 version. When I run it under
access 2007 I find that some queries fail to execute replying the message:

Error reservado (-1524); no hay ningún mensaje para este error.

of course I'm using the spanish version. as a clue, I found in both cases
the error raises in queries with embedded comparison functions (iif).

If somebody can help me I really appreciate.

 

[Allen Browne]

The fact that the tables are linked from an Access 2000 MDB should not cause
any problem.

Is OT a table? Or a query?

If it's a table, then I can't see any reason why this would not work,
assuming the field types are correct, i.e.:
- Estado, MatlEnPreceso = Yes/No
- Piezas, Kilos, Cant, Porsuritr, Surtido = Number (or Currency)
- Uni = Text
- OT and Cod = the same type.

If OT is a query, does it use outer joins?

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Allen thnaks a lot for your interest in my problem. Here I add the SQL
statement:

UPDATE EmbarquesPorOT INNER JOIN OT ON EmbarquesPorOT.OT = OT.Cod SET
OT.Surtido = IIf([Uni]="Pz",[Piezas],[Kilos]), OT.PorSuritr =
IIf([Uni]="Pz",[cant]-[piezas],[Cant]-[Kilos]), OT.Estado =
IIf([Uni]="Pz",IIf(([cant]-[piezas])<1,False,True),IIf(([Cant]-[Kilos])<([cant]*0.05),False,True)),
OT.MatlEnProceso = False
WHERE (((OT.Estado)=True));

As I had been working on this, I found the if I delete the WHERE
statement,
the message dissapears. Anyway, thats useless to the purpose. The
headhache
is that, the application is fully functional under MsAccess 2003. The
application is a 2003 mde file, but the linked databases are Access 2000
files. could this be affecting?

The reserved error means something went wrong that the Access developers
did
not anticipate. It is difficult to guess what that might have been.

Not sure what to suggest other than compacting the database:
Office Button | Manage | Compact/Repair

You can try posting the SQL statement here if you wish, but it would be
very
difficult to trace what's going on without details of the field types.

If your regional settings are Spanish, I don't know what chararacter you
use
as the delimiter. It's defined in the Regional Options of the Windows
Control Panel, and you may need to use that characters in place of the
comma
in the IIf() expressions. For example, if you use ; rather than , you
might
try:
IIf([A] = ; 1 ; 0)
I've no idea whether that could help.

As always, you want to ensure Name AutoCorrect is turned off:
http://allenbrowne.com/bug-03.html

It might be that JET is getting the data types mixed up. If so, you might
be
able to explicitly typecast:
http://allenbrowne.com/ser-45.html

If you have yes/no fields and outer joins, it might be the result of
JET's
inability to handle nulls in logical fields
http://allenbrowne.com/bug-14.html

You could try switching the query to SQL View, and copying the statement
out
to Notepad. Delete the query. Make a new one, switch to SQL View, and
paste
the statement back.

Not sure any of that will help, as I would have expected the same issues
under Access 2003. Perhaps someone else has another idea to contribute as
well.

I'm using the evaluation version of Office 2007 pro. I have an
application
that I was using seamlessly under access 2003 version. When I run it
under
access 2007 I find that some queries fail to execute replying the
message:

Error reservado (-1524); no hay ningún mensaje para este error.

of course I'm using the spanish version. as a clue, I found in both
cases
the error raises in queries with embedded comparison functions (iif).

If somebody can help me I really appreciate.

 

[Elias Moreno]

OT is a linked table and data types are correct. OT and cod are the same type
(text).
Anyway thanks for your help. I decided not to use Access 2007 by now. I hope
Microsoft do something, since I can't cope with an error which has no
further information.

The fact that the tables are linked from an Access 2000 MDB should not cause
any problem.

Is OT a table? Or a query?

If it's a table, then I can't see any reason why this would not work,
assuming the field types are correct, i.e.:
- Estado, MatlEnPreceso = Yes/No
- Piezas, Kilos, Cant, Porsuritr, Surtido = Number (or Currency)
- Uni = Text
- OT and Cod = the same type.

If OT is a query, does it use outer joins?

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Allen thnaks a lot for your interest in my problem. Here I add the SQL
statement:

UPDATE EmbarquesPorOT INNER JOIN OT ON EmbarquesPorOT.OT = OT.Cod SET
OT.Surtido = IIf([Uni]="Pz",[Piezas],[Kilos]), OT.PorSuritr =
IIf([Uni]="Pz",[cant]-[piezas],[Cant]-[Kilos]), OT.Estado =
IIf([Uni]="Pz",IIf(([cant]-[piezas])<1,False,True),IIf(([Cant]-[Kilos])<([cant]*0.05),False,True)),
OT.MatlEnProceso = False
WHERE (((OT.Estado)=True));

As I had been working on this, I found the if I delete the WHERE
statement,
the message dissapears. Anyway, thats useless to the purpose. The
headhache
is that, the application is fully functional under MsAccess 2003. The
application is a 2003 mde file, but the linked databases are Access 2000
files. could this be affecting?

The reserved error means something went wrong that the Access developers
did
not anticipate. It is difficult to guess what that might have been.

Not sure what to suggest other than compacting the database:
Office Button | Manage | Compact/Repair

You can try posting the SQL statement here if you wish, but it would be
very
difficult to trace what's going on without details of the field types.

If your regional settings are Spanish, I don't know what chararacter you
use
as the delimiter. It's defined in the Regional Options of the Windows
Control Panel, and you may need to use that characters in place of the
comma
in the IIf() expressions. For example, if you use ; rather than , you
might
try:
IIf([A] = ; 1 ; 0)
I've no idea whether that could help.

As always, you want to ensure Name AutoCorrect is turned off:
http://allenbrowne.com/bug-03.html

It might be that JET is getting the data types mixed up. If so, you might
be
able to explicitly typecast:
http://allenbrowne.com/ser-45.html

If you have yes/no fields and outer joins, it might be the result of
JET's
inability to handle nulls in logical fields
http://allenbrowne.com/bug-14.html

You could try switching the query to SQL View, and copying the statement
out
to Notepad. Delete the query. Make a new one, switch to SQL View, and
paste
the statement back.

Not sure any of that will help, as I would have expected the same issues
under Access 2003. Perhaps someone else has another idea to contribute as
well.

I'm using the evaluation version of Office 2007 pro. I have an
application
that I was using seamlessly under access 2003 version. When I run it
under
access 2007 I find that some queries fail to execute replying the
message:

Error reservado (-1524); no hay ningún mensaje para este error.

of course I'm using the spanish version. as a clue, I found in both
cases
the error raises in queries with embedded comparison functions (iif).

If somebody can help me I really appreciate.