Search results

If I understand what you are saying... you are saying that if this DLookup fails during login from the login form: Credentials.UserId = DLookup("ID", "tbl_users", "UserName = '" & Credentials.UserName & "'") then when this line in the appropriate data input form fires upon clicking the submit...

I do not know the answer to that question but I can try changing the period to an exclamation mark and see what happens.

and the login form frm_loginform: Option Compare Database Private Sub Form_Load() CheckFrontEnd.CheckFrontEnd End Sub Private Sub Command1_Click() If IsNull(Me.txtLoginID) Then MsgBox "Please Enter Login", vbInformation, "Need ID" Me.txtLoginID.SetFocus ElseIf...

I will post the code for the credentials module and the complete form codes showing how the credentials are checked. Credentials module: Option Compare Database Public UserName As String Public UserId As Integer Public AccessLvlID As Integer Public Function GetCurrentUser() As Integer...

Doesn't Environ grab the windows username rather than the database userid? Their windows username is not necessarily the same as the username they used in the database. In retrospect I should have set the db up to use Environ from the start but too late now.

I just noticed a strange thing happening in my database. I have 2 data input forms that do not create new records but only update information in existing records. The random thing happening is the code behind the forms is set to log the UserID in each record of the persons making the edits...

My apologies for hijacking the thread.

I changed the code to this so it will work with both 32 & 64... this should work right? #If VBA7 Then Public Declare PtrSafe Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" _ (ByVal hwnd As LongPtr, ByVal lpOperation As String, ByVal lpFile As...

I will work on the conditional piling. However I did notice that while for the most part this does what it says but using method #2 I manually upload some files to a folder I named "Attachments" in the directory where the back-end is stored... in the sample db I choose the files from that...

I found something online that fixed it I think I changed this: Public Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" _ (ByVal hwnd As Long, ByVal lpOperation As String, ByVal lpFile As String, _...

Is it possible to update this example so it will work on 64-bit systems? I really want to use method #2 in my db but cannot as this is for 32-bit

The way I did it was to have different main forms all named differently (all the same as each other but only certain tabs each) for each type of user and only have the tabs that are related to them and during login my code checks to see what access level they have and directs them to their own...

In the scope of things it is definitely unnecessary as it will take care of itself but I just wanted it so I can keep track of who is actually using the database and who has even bothered to start using the first version containing the updating feature without having to dig around in the data...

FEVersion = DLookup("fe_version_number", "tbl-fe_version") DoCmd.SetWarnings False DoCmd.RunSQL "UPDATE tbl_users SET Version = '" & FEVersion & "' WHERE ID = " & Credentials.UserId

I'm probably going to get scolded for this but here goes. Now that I have all of this in place... there is no way for me to look in the back end and see who has what version of the front end running on their computer. I understand that they should all be running the latest if it is working for...

I was able to take control of his computer and test whether or not he could get to the back end file location and he could not. Folder permissions was the culprit. As I suspected after ridders references or folder permissions suggestions... our IT department gave some people permissions to the...

Thank you very much both of you for the suggestions. I cannot test on a 32-bit system as we do not have any at my facility. The one in question is in another state. As for the folder permissions.... there is a remote possibility this could be the issue. Our IT department (I think) gave all...

So I have been informed that I have one user who this does not work for. He claims that when the message box pops up alerting him to the new version and he clicks the OK button it just loops back tot he same message box again. I remembered the warning about having the versions correct in both...

I would have to agree. I just noticed in my PowerPoint application there is a big difference in how videos are played back compared to several months ago the last time I made a presentation containing them. Our computers are always under an onslaught of updates pushed on us by out IT...

I forgot to mention in the other thread. Aside from when choosing a date from the picker it does not generate the tray message... only when starting up the program. When manually changing the date in the field then clicking on the form outside the field it will generate the tray message with...