Search results

Just a little tidbit. I normally hide almost everything - so that the casual user won't see things they shouldn't be messing with, but - I always have my Access system set up to show me hidden objects. They show up sort-of half-way grayed out, but they show up. This would have prevented this...

Maybe I don't understand what these routines are for, but, I cannot get them to fire - at all. My intention is to use the Detail_Paint routine to do a little custom formatting, but this routine is called over and over again. So, I want to find a way to trap if/when the form is *first* rendered...

I guess I want to 'pile on', saying that I've run into the exact same challenges trying to include charts/graphs in my Access solutions ----- FOR YEARS. It is the "for years" part that is so frustrating. It's one thing to forego a capability when a solution is starting out. It's another to...

Hmmmm... So, does this not show that 2 bytes are used? You're saying this will always output 2 bytes per character, regardless of the system you're in?

OK --- "This is a test" --- It indeed looks like 2 bytes per char. in your case... Will try to look at it this way. Thanks!

OK... Thanks for looking into it!

I need to determine if Access 2000 (Jet/ADO 4.0) supports the full UTF-16 Unicode encoding standard or if it only supports UCS-2. Anyone know this? (Apparently various resources out there have inconsistent info - indicating it is UTF-16, while still asserting it uses 2 bytes per character -...

Right - so for the date - I was merely trying to handle nulls - I didn't really care what value it took, as long as it set it to something. I probably assumed too much that adding the NZ as written made the problem go away - but it at least "seems" to work. I will double-check it more closely...

Kudos to @theDBguy - as he put me on a track that seems to have resolved this mystery. After doing a little online hunting for "Debug mode behaves differently than run mode" kind of thing - I came across someone with the same kind of problem - but in Excel. Their solution was the same as...

Actually, no - I had not tried that. I JUST tried that - pausing it right before where it complains, and when I step through - it works... Hmmmmm... Does that generate any new ideas?

Interesting. As I've noted - (I think) the query works fine when I hit the play button after it errors... so again - I don't see how it can be a flaw with the query - when it works - just only after it complains... I will double-check this though!!

I tried putting a loop in that error-catching cycle - but still no go. It seems the query won't work when "requested" to be run from VBA - but when "requested" be run by ME - (whether a pre-made query, or simply letting it continue even) - THEN it runs. I find this to be really strange...

OK - but if the query is fundamentally flawed, how is it that it works fine upon hitting 'play' in VBA after clicking Debug? This is why I started the thread thinking it was NOT the query... :) I don't see how the query can be OK and not OK at the same time. It works perfectly if I simply...

Right --- Well - those are not the real fieldnames - sorry 'bout that - as I said - I had to sort of mash up a sample... I think it may be too difficult to troubleshoot here without the real query. I was hoping - though - that the issue was NOT the query - since it CAN run - just by...

Not to light another fuse, but I think we all know Access <> Oracle. But that is kind of the point too. I've built a lot of nice, efficient, handy tools with Access. Is it perfect? No. Does it meet every requirement? No. Is it bulletproof? Not by a longshot. But you can get a LOT done with it...

Funny - I had not heard the "with a rubber mallet" add-on before... ;-) I'll try to hand-jam in something that represents the actual query --- can't really put the entire real thing in here... UPDATE tabMain AS M, tabTemp AS T SET M.Position = T.[Position], M.MoveDate = T.[Move Date]...

True... The exact message was: Run-time error '3113': Cannot update '(expression)'; field not updateable. I guess that isn't all the much more informative - other than it is referring to an '(expression)' rather than a particular field name. I'm trying to put together something I can post to...

True - I'll try a delay to see if that helps any...

Good idea. I did try a "DoEvents" to see if maybe there were some lingering things undone, but it didn't help. Perhaps there is some other command I should run to make sure nothing is lingering?

Also a very good point. Here's yet another strange set of characteristics surrounding this - related to that idea of it actually still being something wrong with the query. As you point out - I originally assumed it was a problem with the query - as we all would of course! I then modified my...