Search results

Thanks for the link, but I'm afraid I'd already seen that... the problem is that it seems to be an actual 2003 error rather than one that's tied to a specific db or bit of code - I've had them try opening a number of different files with different content, including one with no content at all...

I'm getting the same error message when I open ANY database in Access 2003, including blank databses with no content (created to test this error). Does anyone have any ideas as to what could be causing this? Many thanks in advance.