Recent content by tt1611

Thanks for getting back @Minty (the continued value of this forum and site in general proves itself). I've been encountering the weirdest things happen in this app build most of them likely occurring with my new upgrade to Office 365. I deployed the timer changes to my production environment...

Just a follow up. I noticed that when i placed a timer on my main form to rehide all the tables, they no longer appear even if I run any queries. This is the weirdest thing but no worries. Ill keep it pushing

Im not seeing anything special here causing this Just running this query itself caused all the hidden tables reappear SELECT MSysObjects.Name, MSysQueries.Attribute, MSysQueries.Flag, MSysQueries.Expression, MSysQueries.Name1, MSysQueries.Name2 FROM MSysObjects...

The passthroughs are just straight select statements linked to some of the same tables I'm hiding. As soon as the user double clicks on any of them, the hidden table group reappears populated with only the linked SQL tables.

Hello All. Does anyone know why tables I have hidden using vba code Application.SetHiddenAttribute acTable, tdf.Name, False keep appearing after a SQL Server passthrough query is run? The tables are all hidden on load of a main menu based on access rights I have set locally but as soon as said...

HI. I wanted to come back and post a reply to say thank you and that i ended up deploying the app as is. There wasnt going to be any chance that a user would be logging into the app who wasnt already logged into the laptop. This scenario was only happening on my dev laptop. I plan to lock the...

Im starting to think this might be SQL caching the login credentials rather than Access. Im noticing that the queries running under the "wrong" USER ID are all service side system sprocs

So i only do have the only one instance open but does application.quit do it as a safer option?

No its ok and thanks again for all your help. Yes. The app is quit with a docmd.quit button on my main menu. Its after that quitting and relogging in back in using the login FE that im seeing this issue in SQL.

No the user saving the record should be consistent with whos logged in (ie current user). Im going to be using that userID to audit changes to this table in an audit table. RoThomas is not the currently logged in user. That account logged in about 4 logins ago.

Heres this trace. Heres me clicking Save on the form and heres the trace. Note the login user switch to someone else for the save transaction.

Yeah - the login form is presented on every log in.

Which again after testing or quitting the app, I see the audit logout transaction in profiler but the user ID persists even after the app is reopened. Its like it stays persisted then clears out after a set time. So you're saying theres no workaround for this?

Hi all Wondering if I could get some help here for this very bizarre issue. I have created a login form for my FE Access App with a SQL Server BE. The user passes in their SQL Login and password and its authenticated against the server. I am using their ID for table audit purposes. When the user...

AND THAT WORKED JUST FINE. Thanks for your help and very quick response. Very weird this worked in prior office versions. Have a great day.