Recent content by billyr

I need to disable the "X" close on the Access window with my application. I have tried 2 approaches from this forum and 1 from the knowledge base and none of them works with my application. They all seem to gray out the "X" but none disables it. I get no errors at compile or when running the...

Thanks deeda67. I was looking for a magic bullet to avoid passing the updates through a spreadsheet; but, that seems to be the right way to do them. I will likely import the spreadsheet into a transaction table and work from that. I already have 2 boolean "flags" in my tables and will use...

I have the same problem as deeda67; but, I need to automate the table transmission process. I am curious what method you (deeda67) use to transmit the tables back and forth? Any suggestions would be greatly appreciated.

Caine, I have done what you are trying to accomplish using a boolean field in the table(s) and queries. In fact, I have found it helpfull to have "extra" boolean fields (I name them flags.) in several instances.

I have a calendar that I have used with access 97 and 2000. It uses a popup form called by a function attached to a small custom command button. There is public module that comes with it so you can use the calendar with any form for any date. I always place the small command button adjacent...

Here is code I use to print spreadsheets from an access application. It works. You could modify this method for editing; I have done it but cannot find the code now. Dim ExcelObj As Object, i As Integer Set ExcelObj = CreateObject("Excel.Application") DoCmd.SetWarnings (False) With...

Here is code I use to print spreadsheets from and access application. It works. You could modify this method for editing; I have done it but cannot find the code now. Dim ExcelObj As Object, i As Integer Set ExcelObj = CreateObject("Excel.Application") DoCmd.SetWarnings (False) With...

It sounds like 2 fields in the query are getting criteria from the form? Here is a snippit of code that dynamically sets the filter for a form in one of my applications: Select Case Me.frmFilter Case 1 'Show ONLY active resident records Me.Filter = "act = true" Me.FilterOn = True Case 2 'Show...

If the stored query already produces the records you want, why bother with strlinkcriteria at all. Just set the form recordsource to the stored query. stDocName = "Arts" Forms_Arts.RecordSource = ArtsQuery2 DoCmd.OpenForm stDocName

First, I am not sure I am competent to advise; but, I am glad to share what I do. My applications always open with a splash form that requests user name and PW. Once validated I store the users name and security level in a public variable. From then on, I only need to check those public...

I use 2 public variables, one for user name and one for security level. Both are gathered by code attached to a splash form. (I also hard code a user name and PW for my own use) If there is a staff table in the application, I have fields for username and PW, if not I add a user table with...

I have used GHudson's code for some time now and love it. I also like to embed a user ID and pw in the code for my start form to make sure I can get in no matter what the client does with the user table.

I have also been in this bucket of worms. I converted a big Excel application to Access and the user insisted on keeping their, user generated, record IDs for staff, clients, facilities, resources etc. I was very new to Access. I made a table to hold the last count for each and a public...

I think I would have used a subform to display records selected by the cbo on the main form. Just as simple, is putting the (unbound) cbo in the form header with details in the Detail section. Lately, I use the SmartForm addin. There are lots of suggestions here for doing that. The command...

Also in the mix of problems noted here is the current generation of programmers who have no knowledge or concern that "user friendly" is not necessarily "fellow programmer (dude) friendly" or "boss friendly". My years in flight simulation (real ones) taught me to make learning the customers...