Error number: -214217887 --> It doesn't save all the records.

[doma23]

Error number: -214217887
Description: Das Feld ist zu klein fur die Datenmenge, die Sie hinzufungen wollten. Versuchen Sie, weniger Daten einzufugen.

Hi, I've made a particular tool by using Access 2003. With all the computers in my office everything works fine.
I've started testing phase with a colleague in Germany that will need to use the tool as well.
However, when she tries to save some data by clicking on SAVE button, she keeps getting this error message above. On english it means something like "the cell is too small for the amount of data".
The error message is generated by error handling procedure.
When Save button is clicked the records to be saved are from 1 to 5. With one record it seems to work fine, however when more than one record is inserted, then the saving procedure save one or max two records, and give this error message without saving the third or fourth record.
It's worth to note that she is using Access 2007, but I've tried to run the tool from Access 2007 from my home computer and it worked well.
I was searching for a solution, and I found something that suggested increasing MaxLocksPerFile through registry or through code. If I do it through code, I need to use DAO. The problem is that I use ADO procedure. I've tried to guide her through changing the registry value and increasing the MaxLocksPerFile , but she doesn't have these privileges.
Is the MaxLocksPerFile problem or something else? It's weird because database is quite small, cca 1400 records, and saving procedure is nothing out ordinary.
Is there anything I can do?

Tnx!

Edit:
This is the error message that appears when I'm not handling error myself. It's on German, however the OLE is mentioned which gives me some indications that the problem could be with references?...:

[doma23]

UPDATE:
I've checked the References on German System, they are the same as on mine system. Just one small difference that shouldn't affect the tool.
German system with Access 2007 is using "MS Access 12.0 Object Library" while my Access 2003 system is using "11.0" version.

[NeoPa]

Doma23:
Just one small difference that shouldn't affect the tool.
German system with Access 2007 is using "MS Access 12.0 Object Library" while my Access 2003 system is using "11.0" version.

What on Earth would lead you to believe that running a project designed on an Access 2003 system, on an Access 2007 system, would not be likely to cause you problems?

[doma23]

Couple of things.
On my home laptop which is using Access 2007, the same tool works just the same as on the office system which uses Access 2003.
Secondly, I have already built and designed some tools by using Access 2003 which are working just fine on German Access 2007 systems.
Third, I've never read anywhere that the system designed by previous Access versions shouldn't work or should cause any significant problems like the one I've described, when run on the new Access version. Which also seems kind of a logical considering that I'm running it on upgraded software, not downgraded?

BTW. The error message means: "The field is too small to accept the amount of data you attempted to add" -- I've checked all the fields, they should be formatted well. And still it remains mystery to me why it would work just fine on other systems if this was the problem.

[NeoPa]

Doma23:
On my home laptop which is using Access 2007, the same tool works just the same as on the office system which uses Access 2003.

That would have been helpful to include in the question I suggest.

As for not coming across such problems, I don't even use Access 2007, yet I have come across reports of such problems on a number of occasions (from questions here on Bytes). While I agree, that in an ideal world, such things would not happen, they do. Libraries for different versions particularly, can throw up differences which cause projects designed on one system to fail on another.

You say that it works on a 2007 system at home. That may be important, but equally, it may simply be that the system isn't used as fully at home as it might be in a working, live, environment. I don't know. I don't have access to much of what you do, but I have to rely solely on what you do tell us, and my other experience. My experience tells me not to expect things to work 100% when moving across versions. There are web pages available that list known incompatibiliti es.

There's not really enough information available in the thread within which to search for whatever might be causing the issue. This is not a fault. It's simply the nature of such problems. If you knew where the problem was, you'd not need to ask for help I expect, and without knowing what you're dealing with, it's next to impossible to post the important information. Unfortunately, I'm still left with very little I can say to help here, more than I have already suggested. Where I'd look is in the compatibility areas between the different versions, but I can see why you may be convinced already this is not where the problem lies.

Please post anything you manage to find, as I'm interested to know eventually what the cause proves to be.

[doma23]

NeoPa:
That would have been helpful to include in the question I suggest.

Actually, I have mentioned it when I wrote:

It's worth to note that she is using Access 2007, but I've tried to run the tool from Access 2007 from my home computer and it worked well.

Anyway, it's true that even though the version of the Access is the same on my home computer and on the German office system, there are differences because on my home computer I'm testing tool locally, while on German system it's being tested through network, as the tool is located on a shared folder on a network disk.
Also, there might be different Service Packs installed. Just an idea what could go wrong.

Also, on both error messages (the ones that appears with and without error handling procedure) there was no debug button on which my colleague could click and read me the highlighted line.
Although she is not so VBA familiar, I will guide her through setting the breakpoint at the start of saving procedure to determine where exactly does it breaks.
Hopefully that will give me a little bit more information.
I'll post whatever I find here.

Tnx.

[NeoPa]

Doma23:
Actually, I have mentioned it when I wrote:

You're quite right. It wasn't in your second post with the statement, but I should have reread the first one again, so I apologise for that. Your explanations are actually quite good generally, especially considering you're working in Italian mainly.

As for the separate systems, I would think first about making sure all are fully up-to-date with all the service packs. There are still possibilities for differences even after that, but at least that will minimise it for you.

Once that has been done, and if you are still experiencing the problem, try taking out the error handling code, and letting your colleague run the tool until it crashes. She would need the debug setting to be set to allow the code to break to the IDE (From the Integrated Development Environment - or VBA Editor - select Tools / Options / General tab / Error Trapping then either Break on All Errors or Break in Class Modules.), but once that is set, she can call you to talk through any details you may want her to find for you. Debugging in VBA may help you if there is anything there you're not already familiar with.

Problems like this are not something I can just hear about and tell you the solution to I'm afraid. It's far too uncommon for that. Certainly within my experience (which is all I have to work from). I will help as and when I can, but I can't promise much I'm afraid.