Search results

Yes, that's what I am talking about. You'd think there should be a place to look at VB references (to controls) or to tell it to update the spelling. But it's mainly the conpact on close issue (that I just noticed since I had this vbe spelling issue) that forces me to rebuild from scratch, like...

Yes I did. I followed those decompile instructions to the letter. The "compact on close" issue puts a spin on it though, the compact completes so quickly that I don't know if I hit <Esc> in time to stop it or not.

Yes that's what we are talking about, form controls. The problem is (a very minor one), I changed them in the forms but vbe won't allow me to change them to match now. Capitalization change only - for programmer readability. I try to do a "replace" "replace all" but the editor instantly...

No it's a split-database on an institutional network with a BE that contains 4000 records of personal information, confidential. Thanks for the offer though.

Yes I just did (and learned how here: https://www.devhut.net/2012/04/16/ms-access-decompile-a-database/). I learned some more about vbe and Access. It lost about 500KB. Upon finishing, it still does the same thing. But here's the kicker: now my db FE is compacting again when I close it...

Hello. I have been redoing some of my old fieldnames in Access, there is several of them I want to fix capitalization in. I have fixed them in the forms, tables, and queries. But when I go into the visual basic editor and attempt to fix the capitalization, the editor keeps undoing it, even...

When you press "debug" at the error, what line and text highlights?

Please post your conditional formatting condition rules.

Or you need to convert to a number like "Val(me.txt_NewVolume)" etc. then compare. Note this method will fail when a user enters something other than a number, any other characters, so this method is not recommended. Just telling you to help your understanding. Also, wondering where you get...

I would run an update query on each of the related tables, replacing the duplicate PK number with the proper one. Is that what you mean by "brute force?"

I wasn't "compiling to MDE" FYI, accde. GTK, gaining wisdom, TY.

Oh, I found out how to work on this, searched and found this: In: https://www.access-programmers.co.uk/forums/threads/makimg-accde.307471/ Already found a vba error in my custom module. Thanks anyway.

I don't understand this, as I only have 20 tables, 47 queries; and open a max of a few recordsets per form, usually only one form at a time. Oh well, I've never used compiled db anyway.

I made some functions to deal with this: Public Function RmvPunct(InputStr As Variant, Optional StopAtComma As Variant) As Variant '.................................................................... ' This simple function removes punctuation, and other non-alphanumeric ' non-numeric...

I believe it's the FE that caches, not the BE.

Thank you, oh yes of course I do, even previous step backups. :)

Well, after the following procedure, I have corrected the problem, along with speeding up the load/exit cycles, it now closes in 10 seconds (remotely): Started new empty FE database. Imported the (small) tables from the original. Linked to the BE tables manually. Forged each Query from scratch...

Are you working with a web-based database or BE? Try turning on 'clear cache on close.'

Yes I have replaced these occurrences with acFormAdd, and all is well now. Thank you all.

No, I didn't know about it, but it appears to have been only a problem if you are accessing a USB drive remotely. I do appreciate your concern Doc.