Search results

After I close Access (via the 'X' or 'Exit') I still see MSACCESS.EXE in my process list. This only happens when I run this piece of code: Public Function GetEmployeeStore(lngEmployee As Long) As Long On Error GoTo GetEmployeeStore_Error Dim conn As ADODB.Connection Dim rs As...

I'm sure most people use Windows shortcuts to open their secured databases, but I found that it didn't always work (depending on which computer I used). Editing a shortcut is pretty confusing since the command is all on one line. I decided to make a batch file to open my secured databases...

Link Fields Are More Than Just A Good Idea Okay, here is a case of using code when I don't have to. Usually I don't use Link Master Fields or Link Child Fields, I just add code to filter the subforms whenever the record changes. Usually it doesn't make any difference (except for maybe slowing...

Done Deal! I can't believe I didn't try this earlier. This was the piece that kept giving me a lot of trouble: ([Store Change].EffectiveDate)=( SELECT MAX(EffectiveDate) FROM [Store Change] As SC1 WHERE SC1.EmployeeID=[Store Change].EmployeeID ) So I changed it to this: ([Store...

Well, I give up. I really wanted to have all of the important information in one query. I honestly don't see why Access is making such a fuss. So it looks like I'll have two seperate queries and perform DLookups on one of them (joining them in the form would give me the same trouble). For...

I didn't think about this at first, but it seems like important information now. I'm trying to join two queries, one of which is a crosstab query. The solution is supposed to be to fill in the Parameters, but I don't know what to put or where to put it.

Here's the root of all my troubles: SELECT EmployeeID, NewStoreID As HomeStore FROM [Store Change] AS SC WHERE EffectiveDate=( SELECT Max(EffectiveDate) FROM [Store Change] WHERE SC.EmployeeID=EmployeeID ); This query works perfectly fine by itself. It's supposed to find the most...

Well, I didn't mean what I said literally. I'm using this as my calculated control source: =[FirstName] & " " & [LastName] Those are the field names and not control names. I also have this calculated control source to show the employee's title: =GetEmployeeTitle([txtEmployeeID]) That one looks...

I have a basic form that shows employee information. A few of the fields are calculated or lookup fields. Starting with the first record I can go thru all of them just fine (I don't see any errors in the fields). If I look at my 2nd record twice then my combined name field (first name + last...

Damn. Really crappy luck. There really isn't a better name for that table so I don't want to rename it. I can get the job done using lookup functions anyway.

I've done double and even triple joins before, but this isn't working for me, probably because I'm using a SELECT statement instead of a table. Here's the basic (working) query: SELECT Employee.*, NewPositionID AS [Position], NewStoreID AS [Store] FROM Employee LEFT JOIN ( [Position...

Okay, okay, before anyone thinks too hard about this I fixed that problem. I grouped the records by Last Name, First Name, and Reservation ID (in that order). So each child is with their correct parent and the parents are listed by last name then by first name. I also had a problem of records...

I'm using two tables to make a "guest list" report. One table has general reservation info including a guest name. The other table has info on each guest's children. So one reservation (guest) can can have 1 to 6 children. I have a query setup that joins each reservation and each child based...

I figured that part out already, but better it was answered and not just left hanging there.

KeithG's method should add a little extra security, but it sounds like a bit of "reinventing the wheel". You should be able to emulate all of the security measures of the build in user-level security, but that would require a lot of coding. And just because someone opens a database with a...

Well, whenever you secured the database it should've made a backup (.bak file). Just change the extension to mdb and that's your database. Don't have the backup? I can't help you then. I get the same error you get every time I secure a database.

My idea worked, sort of. I secured my backend and I was able to read but not edit the data on the frontend. However, my grasp of user-level security is still very lacking. In my case I either get asked for a password all the time (even when using databases I didn't secure) or I never get...

I'd like to know the answer to this as well, but I also have a suggestion (which I have a feeling will be debunked). If you secure the backend that should make the tables safe. I'm assuming that if the backend is secure you can't mess with the tables without proper permissions (even when using...

Apparently Access thinks we're all robots and we don't care if there are newline characters in the queries or not. Well, I'm not a robot and sometimes my queries are impossible to understand without adding a few new lines. Whenever I save and reopen queries most of the newlines I had are...

It looks a bit odd on my form but using a combo box really does the trick. I can bound a column and then hide it (by making its width 0") so they think they're saving some other value. I think using the combo box method is more reliable than putting a procedure in the AfterUpdate or...