Multi user login screen - question about tracking logged in users

[zmbd]

Close your database and reboot the pc.
Reopen your database.
From the MAIN Access window... not VBA...
You must do this from Regular old Access GUI (forms, reports, etc... showing are ok).

Press <Ctrl-G>
Please post back what happens...

[NeoPa]

I had no idea Ctrl-G worked from there too Z. I've always used it from the VB Editor window, It seems it will work from both.

ANewUser:
I am still struggling to activate the debugging mode.

If you're referring to breaking into code execution, then it's not necessary for this. Please just follow the instructions exactly as posted.

[zmbd]

super-secret-chemist-formula...
Now I must send the MIB out to erase your minds once OP starts the self-destruct sequence (1-1A, 1-1A-2-2B, 1-B2-B3, 0-0-destruct-0)

@ANewUser
Dont red-dot your code to goto to break mode.
Use STOP
Red-Dots will mess with your code forcing at minimum a decompile/recompile. It is a known bug in the editor (at least to those of us that do a lot of programing) the MS doesn't seem to (or care to) want to fix. Their reply has been along the lines of "well... don't use it then... use the STOP like we do (use your best dunce-mode voice)"

I must have the answer to the instructions given in #46

[anewuser]

Hi I tried running that line (from post #44) in the immediate pane. I was still able to login as normal but usyscurrentuser wasn't updated.

[NeoPa]

The only reason to use the code from post #44 was to post the results back here in the thread. There were no changes made to your project in that code whatsoever. If you read the post again you'll see clearly what was asked for.

[anewuser]

Hi Everyone, I know it has been a while since my last post and this is because everything now works fine and i haven't had the time to get back online to thank you all for all of your help.

[NeoPa]

I'm pleased to hear that, but it may be helpful to anyone reading the thread if you posted an explanation of why it wasn't working and what you changed at that point to make it work.

[anewuser]

I was able to login as normal using the code from post 35. However, it was not updating the usyscurrentuser table. I fixed this by changing the source of the form from nothing to the usyscurrentuser table. This worked, now when I log in it adds a new record into this table. Probably not the best way to sort the problem but it has worked and I am happy with it.

[NeoPa]

Probably not a bad solution as it happens. It won't normally add a new user BTW, but update the existing one. At least after the first time. This is lucky, as if it added one it would be fundamentally useless to the process.

Z:
It is a known bug in the editor (at least to those of us that do a lot of programing) the MS doesn't seem to (or care to) want to fix.

I consider myself reasonably experienced in that area, but I hadn't heard that before ;-) I'll certainly bear it in mind in future. It does mean the code needs to be recompiled anyway - unless the object is closed without saving I suppose. Food for thought.

[zmbd]

Usually happens when the breakpoint trips and/or stepping thru code: then code is edited while in the debug state. Google "phantom break point." Been around since at least 97 when I first encountered it... wouldn't be surprised if there isn't something here on BYTES :)
(found one: http://bytes.com/topic/access/answer...en-starting-pc :)

[NeoPa]

Oh that issue. I've had that a few times. Like one of the posters in the linked thread, I will simply add an edit, recompile and save. Typically though, although I will change code while running during the development cycle, I will redo it for release, and I never save an object with any breakpoints set, for that reason. Sometimes, with an object that is already supposed to be ready for release, but I have to make small tweaks to it, I'll close the object without saving, but after I've copied all the code to the clipboard, then reopen it, replace the code with the new, and close and save it then.

I've never seen this talked about before though. I just came up with my work-arounds after experiencing the problem a few times.

I still use breakpoints though, just within the parameters explained above. Clearly it makes sense to advise against relying on them for general consumption though. Good work as usual :-)