Validation Expression (Access 2000)

Topic

New Reply

I’ve never seen this error, and a Google search does not turn up anything useful. Could it be a references problem?

Reply | Quote

Replies

I don’t think so, but I will investigate this at the client site.

I run Access 2002 and they run Access 2000. One of the steps I get them to do is to:
1. Uncheck Microsoft Outlook 10.0 Object Library
2. Check Microsoft Outlook 9.0 Object Library

I will ask them to check any missing references.

Reply | Quote

I don’t think so, but I will investigate this at the client site.

I run Access 2002 and they run Access 2000. One of the steps I get them to do is to:
1. Uncheck Microsoft Outlook 10.0 Object Library
2. Check Microsoft Outlook 9.0 Object Library

I will ask them to check any missing references.

Reply | Quote

A client runs a conversion form I wrote but it comes up with the following error:

CANNOT PLACE THIS VALIDATION EXPRESSION ON THIS FIELD.

Does anyone know what this means.
I thought I would try this forum before going out to the Client site and stepping this form instruction by instruction.

Reply | Quote

I’ve seen the error but I don’t recall the circumstances. Check and make sure there is no filter string, stored in the form or being passed to it, that might be triggering this.

Reply | Quote

Could it be that I develop in Access 2002 (Access 2000 file format) and they have Access 2000. What I do is to copy my Access 2002 DB to their system and they execute this DB under Access 2000.

Could there be a problem here?

Reply | Quote

Oh, yeah, that could definitely be it. When you say you develop in 2002, I assume you’re using the 2000 file format, but there are still things that were introduced in XP that simply won’t work in 2000, like the Replace function in a query.

Reply | Quote

I don’t think that’s it. I have pruned it down to one table. I have tried to copy this table into the same database under a different name and I get the error, however it still copies the table.
Unless you can steer me in another direction, I will delete one field at a time and try to copy the table until the error does not appear (then I will know what field is causing the error).

If this does not work, I will recreate the table from scratch in design view and delete the strange table (after all it may have some slight corruption).

I have also tried to create a blank database and import all the objects, but it stops for this table.

Reply | Quote

If there’s a memo field in the table, start by removing that. They’re the most frequent cause of table corruption. If that works, you may be able to create a new table with the same structure as the old and append all the fields except the memo field to it. After that, try an update query to update the memo fields from the bad table. If it’s just a record or two, you’ll get all the but bad ones.

Reply | Quote

I had better explain this a little more.
I have a form which:
1. Saves the table relationships to a table
2. Deletes all tables
3. Imports tables from another database
4. Re-establishes the relationships between the tables.

It does more than this but it’s mainly to queries, macros, etc.

Do I need to refresh the tabledefs before further processing.

This form has been working for quite a while now, it’s only the last 2 weeks it’s been playing up.

Reply | Quote

I had better explain this a little more.
I have a form which:
1. Saves the table relationships to a table
2. Deletes all tables
3. Imports tables from another database
4. Re-establishes the relationships between the tables.

It does more than this but it’s mainly to queries, macros, etc.

Do I need to refresh the tabledefs before further processing.

This form has been working for quite a while now, it’s only the last 2 weeks it’s been playing up.

Reply | Quote

I have been saving my databases almost everyday (or thereabouts) for the last couple of months (I have 42 backups).
I can save the backup and open the saved backup and try to copy the table in question and it immediately brings up the error.

Would this mean my Access installation is corrupt?

Reply | Quote

Another strategy you might try is to open a recordset on the table and try to copy the table record-by-record using DAO – when it fails you would find the record – or records – that appear to be corrupt. I suppose it may also be that the tabledef is actually corrupt, but in that case I would expect more serious problems (not that what you are trying to deal with isn’t serious!).

Reply | Quote

i have tried that, it works ok.
I can copy the table, the dialog box springs up and after you click the dialog box I find that the table has been copied in it’s entirety.

Although it loses the Format and Input Mask properties, and for any text field it sets the Allow Zero Length property to Yes.

This would indicate to me that the tabledef is ok too, mind you I could be wrong.

Can you tell me where at Microsoft I can find out about this error.

Reply | Quote

I was only able to find information about this error in two places – http://www.vb123.com/toolshed/01_bugs/access_errors.htm%5B/url%5D and http://dbforums.com/t631006.html%5B/url%5D – and it seems to be related to Access 2002. Are you attempting to apply validation rules to the table in question? For example are you importing data into a table where the Required property is set for a field, but the data coming in is Null?

Reply | Quote

Where on earth do you get these links Wendell. Thanks for your time to go and search for these links, I really appreciate this.

Unfortunately they don’t mention what the solution is.

As you suggest I will check the Required Property on all fields as well as Allow Zero Length, etc.

Reply | Quote

Aww shucks – wasn’t much! Actually, I did a Google search on the error text and found them. But absolutely nothing on the Microsoft site. And you are absolutely correct – no mention of the solution. Which suggests to me that it may really be a validation issue with the data you are bringing in.

Reply | Quote

Have you noticed lately that you can’t find errors on the Microsoft site for anything but the current version? You can search on the specific error message and even the number and turn up no articles even though you know there was an article on that problem. When they move the old stuff to MSDN, they seem to drop it from the MSKB indexes entirely.

Reply | Quote

Have you noticed lately that you can’t find errors on the Microsoft site for anything but the current version? You can search on the specific error message and even the number and turn up no articles even though you know there was an article on that problem. When they move the old stuff to MSDN, they seem to drop it from the MSKB indexes entirely.

Reply | Quote

Aww shucks – wasn’t much! Actually, I did a Google search on the error text and found them. But absolutely nothing on the Microsoft site. And you are absolutely correct – no mention of the solution. Which suggests to me that it may really be a validation issue with the data you are bringing in.

Reply | Quote

Where on earth do you get these links Wendell. Thanks for your time to go and search for these links, I really appreciate this.

Unfortunately they don’t mention what the solution is.

As you suggest I will check the Required Property on all fields as well as Allow Zero Length, etc.

Reply | Quote

I was only able to find information about this error in two places – http://www.vb123.com/toolshed/01_bugs/access_errors.htm%5B/url%5D and http://dbforums.com/t631006.html%5B/url%5D – and it seems to be related to Access 2002. Are you attempting to apply validation rules to the table in question? For example are you importing data into a table where the Required property is set for a field, but the data coming in is Null?

Reply | Quote

Another strategy you might try is to open a recordset on the table and try to copy the table record-by-record using DAO – when it fails you would find the record – or records – that appear to be corrupt. I suppose it may also be that the tabledef is actually corrupt, but in that case I would expect more serious problems (not that what you are trying to deal with isn’t serious!).

Reply | Quote

I have been saving my databases almost everyday (or thereabouts) for the last couple of months (I have 42 backups).
I can save the backup and open the saved backup and try to copy the table in question and it immediately brings up the error.

Would this mean my Access installation is corrupt?

Reply | Quote

If there’s a memo field in the table, start by removing that. They’re the most frequent cause of table corruption. If that works, you may be able to create a new table with the same structure as the old and append all the fields except the memo field to it. After that, try an update query to update the memo fields from the bad table. If it’s just a record or two, you’ll get all the but bad ones.

Reply | Quote

I don’t think that’s it. I have pruned it down to one table. I have tried to copy this table into the same database under a different name and I get the error, however it still copies the table.
Unless you can steer me in another direction, I will delete one field at a time and try to copy the table until the error does not appear (then I will know what field is causing the error).

If this does not work, I will recreate the table from scratch in design view and delete the strange table (after all it may have some slight corruption).

I have also tried to create a blank database and import all the objects, but it stops for this table.

Reply | Quote

Oh, yeah, that could definitely be it. When you say you develop in 2002, I assume you’re using the 2000 file format, but there are still things that were introduced in XP that simply won’t work in 2000, like the Replace function in a query.

Reply | Quote

Could it be that I develop in Access 2002 (Access 2000 file format) and they have Access 2000. What I do is to copy my Access 2002 DB to their system and they execute this DB under Access 2000.

Could there be a problem here?

Reply | Quote

I’ve seen the error but I don’t recall the circumstances. Check and make sure there is no filter string, stored in the form or being passed to it, that might be triggering this.

Reply | Quote

A client runs a conversion form I wrote but it comes up with the following error:

CANNOT PLACE THIS VALIDATION EXPRESSION ON THIS FIELD.

Does anyone know what this means.
I thought I would try this forum before going out to the Client site and stepping this form instruction by instruction.

Reply | Quote