Expression in argument 5 - invalid value

[Guest]

Hi all - Access 2002XP - WinM

I have a form that is now giving an error on save of "An expression in argument 5 has an invalid value.

This is my first day back to work after a 3 month illness absence, and the last day I made an entry to this form it worked fine. When I tried to enter data into the entry form today, I get the error message. The person filling in for me was doing the entry durng the time I was out. The form in the copy of the db as of 12/1/03, which was the last day I entered data, does work fine. While I am getting this error message, it appears the entry is being saved, but, not being cleared from the entry control boxes or responding as it should. There were several other descrepencies that were found in the current db that I have been able to resolve, but this one remains elusive. ;-(

I have tried the following

1) Replaced the entry form with a copy from the 12/1/03 (working db
2) Imported all files into a new databas
3) Imported a copy of the table the entry form is based on from the 12/1/03 d
4) Checked all control box detail
5) DB is set for Compile in close

I don't now what the error is referring to, so I am not sure at this point where else I should troubleshoot. I also found that at some point, someone had set up the D drive, where my database files are kept, to be acccessed remotely. This could only have been done by our IT dept, as I, nor anyone else in our dept. have permission to do such a thing. But, pointing fingers at the IT in our company is like accusing the Pope. And I don't want them messing in the database

I would truly appreciate it if someone would please explain what this kind of error pertains to so I have some idea were to go next to try get this issue resolved.

Best regards
Jan :

 

[Guest]

Please disregard, problem resolved.

Jan

 

[Jeff Conrad]

And the solution would be????
Sure, just drop a wrapped present at our feet and say "Do Not Open."
;-))

Jeff Conrad
Bend, Oregon

 

[Jan Il]

And the solution would be????

Sure, just drop a wrapped present at our feet and say "Do Not Open."
;-))

Well..it's a bit confusing, and I'm not sure what or how it happened, other
than someone decided to do some revising on their own. How they did is very
infuriating and disturbing story, but, it happened during the 3 mos. I was
out on medical leave of absence, so hard to point a finger.

The form had originally been set up to save the record from a save button
which had code to check for duplicate entries for all three series of entry,
monthly, quarterly and 1 year. In fact, the very code that *you* helped me
with to do this great task. ;-))

It seems that an attempt had been made to revise the code, and failing hat,
the Save button was being bypassed with a Tab event situation, so the Save
button would not be utilized. When I returned to duty this last Monday and
began entering data in this form, I clicked the Save button to save the
record as usual. That is when I was confronted with the error. As I stated,
I tried troubleshooting in every way I could think of to no avail.

I finally decided to take each step one at a time, with a process of
elimination, and it finally dawned on me what was happening. I checked the
code on the Save button and found the errors. I then restored the code and
revised the Tab sequence. Then the process worked as it should.

I am just surprised that I got the error that I did. I guess that is what
threw me off. It did not make any sense to me in view of what was happening
and it misled/confused me.

So..there it is. Now just don't step on it....'k.. ;-))

Jan

 

[Jeff Conrad]

Hi Jan,

Well..it's a bit confusing, and I'm not sure what or how it happened, other
than someone decided to do some revising on their own. How they did is very
infuriating and disturbing story, but, it happened during the 3 mos. I was
out on medical leave of absence, so hard to point a finger.

(IT Dept, IT Dept, IT Dept, IT Dept........)

The form had originally been set up to save the record from a save button
which had code to check for duplicate entries for all three series of entry,
monthly, quarterly and 1 year. In fact, the very code that *you* helped me
with to do this great task. ;-))

I plead insanity.
(Yeah, there's a stretch)

It seems that an attempt had been made to revise the code, and failing hat,
the Save button was being bypassed with a Tab event situation, so the Save
button would not be utilized. When I returned to duty this last Monday and
began entering data in this form, I clicked the Save button to save the
record as usual. That is when I was confronted with the error. As I stated,
I tried troubleshooting in every way I could think of to no avail.

Nothing came up in my KB search either on that error.

I finally decided to take each step one at a time, with a process of
elimination, and it finally dawned on me what was happening. I checked the
code on the Save button and found the errors. I then restored the code and
revised the Tab sequence. Then the process worked as it should.

Humm....weird.
At least you have it working again.

I am just surprised that I got the error that I did. I guess that is what
threw me off. It did not make any sense to me in view of what was happening
and it misled/confused me.

Thanks for the update on this.

So..there it is. Now just don't step on it....'k.. ;-))

LOL!!

Jeff Conrad
Bend, Oregon

 

[Jan Il]

Hi Jan,

(IT Dept, IT Dept, IT Dept, IT Dept........)

Ya wanna try..giving out my logon pass word? But..no one knows who?
Or..setting up the D:\ drive on my hard drive...where all my documents are
kept, so it can be accessed remotely. IT personnel are the only ones with
permissions to do this. However, no one knows who did it? Nor who
authorized it? But..you see...there's a good reason for it if they should
find out who did it. Even it it's just because...they can. :-((

I plead insanity.
(Yeah, there's a stretch)

Ahp!! Too late... ;-))

Nothing came up in my KB search either on that error.

Nothing found in Google either.

Humm....weird.
At least you have it working again.

Fortunately it was relatively easy ....as opposed to difficult...to find the
cure. However, I have not had opportunity yet to try all areas, so, I can't
be sure there are not more problems ahead.

Thanks for the update on this.

No prob. I am just puzzled that I got an error that does not seem to exist.
I mean...you'd think that if the error message was written, it would be in
reference to something, somewhere, and there would be something about it,
even if like many others, it was wrong? That is what made it so difficult
to try to troubleshoot. :/

Jan