Search results

Upon trying this approach of using a query - the system STILL won't allow me to delete that file. So annoying. I don't have the query open or anything. I just don't get it. I may have to resort to forcing it closed after all. (This all seems so unnecessary. I can't think of any reason for Access...

Hmmmm - interesting. I've only recently seen/used this connect-string-in-a-query thing. I will experiment with this - as it is perhaps somewhat simpler than all the file-handle stuff - assuming this approach works. Thanks!

Very interesting Doc_Man - thanks very much. I think I may have some code around that I found before that forces an Excel file closed (when the user forgot to close it.) I'm betting it looks a lot like what you provided. I vaguely recall it looked for file handles etc. Not sure if there is...

I'm not seeing any problems with deleting the table. It is when I try to delete the file that the table was linked to that I run into the permission issue. Access still has its hooks in it. I've also tried refreshing Access's Tabledefs collection, after deleting the table (since I just...

I'm trying to process some large text files, and although I can import them, I would rather link to them pull the data I need and then unlink and process the next file. Turns out I need to do some clean-up of these files before working on them (removing junk up top - leaving nice delimited...

Right - well - I'm doing this on a form because I do intend to support activities/operations etc., so data will change, and thus a Report will not do. I'm trying to mimic some formatting that I've done on Reports, but on a Form. I considered Conditional Formatting, but the only way a choice...

I was thinking maybe there would be a way for me to discern when it had 'painted' the last item, and use that as my trigger for flipping the Boolean that I'd later use to ignore any mouse movements and clicks etc. as far as the formatting. Not sure if there is a way to discern when it is done...

I just don't understand why an event is listed, but then ignored. Why do they even list it as being available for a form - but - not really. It's a red herring... Ha...

The only reason it needs to be in the paint event is that the formatting is to be changed line-by-line.

So - I'm listing some items on the form (not a report... I've done this with reports and it is not as troublesome as they are essentially not dynamic.) I would like certain repeated fields to not show - like not repeating the parent unnecessarily. I intend to simply paint the font white. This...

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?