Instead of using the reports record source property to view the records try useing the reports recordset property to retrieve the data from an open recordset. You can use the Load event to open the recordset and set the reports recordset property to the recordset you just opened. I believe this...
I have done something like this before. What I did was use the FileSystemObject to first see if the path existed (read access), then see if I could create a text file, and then check to see if I could write to and delete the text file.
You could use an update query but why would you want to store this if you can use the above expression to get the same result? Seems like a waste of space.
Yeah I saw that but thanks. It is a challange explaining to the project group why they got ride of ULS. I agrue that honestly since Access is a file server db your data is not truely safe anyways becuase the users need access to the file. So if someone knows what they are doing its only a matter...
Has anyone seen any good links to explain why Microsoft discontinued User Level Security in Access 2007? If so can you post the links. There is a debate at my work and I want to get all the infomation possible. It is my understanding that the beefed up the encryption on the standard password so...
So basically when the record is created you want to populate the date? If so go into the table design view and in the date fields default value Put either =Date() or =Now()