Search results

OK, so I learned something for sure. I was looking at the validation rule for the Due Date field in the Table Design Mode. I had NOT looked at validation in the Properties for the table. Other than the possibilities that my back end is corrupt, it seems that is it. I'll try it out and report...

I rechecked again. Validation rule is clean as a whistle in the backend and in the linked table. Now its possible I (stupidly) tried to delete it in the linked table first and then deleted it in the Back end table. If my memory works I believe I had done all the data validation stuff before I...

That is what it looked like before I deleted it. I was surprised to see that it is there for you. I had checked and rechecked that it was gone. I don't have my original 'uploadver' file. I wanted to check it. All I had done though was to zip it up. But that does explain somewhat. It was...

I am Still interested in figuring out what is going on but I have successfully coded around it. In the after update for DueDate, I am checking the day of week it is. If it is Saturday I am adding two days, If it is Sunday I am adding one day. And as expected my unwanted check for a weekend...

It always helps to have a second pair of eyes on it. This is the backend with a lot of records removed. What is your opinion on the /decompile thing? Or rewrite it from a blank slate. Sounds scary but probably not nearly as awful as I am imagining it, right ? Its starting to 'feel'...

Quick question. are you talking about decompile for the front end? or back? or both??

Yes , I'm convinced its table based. The validation text is exactly as I had originally programmed it. It being there in the first place isn't a mystery. I want to get rid of it so I deleted the line for data validation and validation text form the table design view. Expected it to go away...

Here is the latest working. Working doesn't mean the behavior for the DueDate field is correct. As far as I know that has always been the case. A bit more background. Some time after I had put in the input validation, I coded such that the due date was just always calculated to be on a...

You mentioned queries. I hadn't looked there. I will. Cross field validation? No, don't think so. I only check if the day number was a weekday. I did have a 'double validation' at one point. The table had the weekday thing and the form had a greater than today validation. They are both...

Earlier today I was doing some trouble shooting in which I would make a form move then check the result in the back end table. I didn't always see what I expected but I did clearly see data going into the back end that I personally had put in the form on the front end. And I had deleted the...

No prob. It will take a minute. So I copied the back end, gave it a different name. Deleted the DueDate Field. Added a new field DueDate. Of course I did NOT add anything to the Validation Rule for the new DueDate field. I went to the front end. Deleted the linked table. Then made a new...

I went back to check behavior and got the same but I also noticed the error message says error '3316'. Not sure if that adds but <shrug>. Also exact text of the error box after Run-time error '3316': is: You Entered a Due Date on Saturday or Sunday - Please correct. I am almost certain...

I checked all forms in the database and looked for anything referencing DueDate and even ended up deleting a couple forms I didn't need. I DID find a validation in the form with the bad behavior but that was >Date(). Still I deleted that as well just to be sure, same behavior.

I made the linked table a local table. I deleted it. then I made a new linked table. Same behavior.

The issue is that I get an error when a form is refreshed. Debug shows the Me.refresh line of code. The 'error' is that the due date is not a weekday. I tracked that back to a validation rule that I had put into the table. It was behaving properly, I just didn't want that behavior any more...

Yes, I actually had the same thought as that would give complete control of the output. I temporarily remain hopeful I can 'fix' what I have for now out of pure laziness :)

I am using ColumnHistory to keep track of changes to a form. When a control on the form is changed then a sub is called to add an entry to the Note field. The code is very simple: Public Sub AddHistory(frmControl As Control, ctlName) Forms("frmDocDetail").Note = ctlName & " Changed to " &...

Thank you for your help. A LOT of progress was made today. Since I was only interested in the data that was on the active form I didn't really use the query function at all. I just built a string that contained the few items I wanted, used insertinto to put them in a table to hold them. I...

thank you for the tips. right or wrong, I tend to get something working first then go back and clean up to best practices. Although I sometimes forget and something this this (a warning turned off) will com back to bite me later.