Search results

I'm not sure this is the right place nor am I sure Access is the right application but here goes. I have around 1000 photos of students, and they are named (for example); 05162xxxxx.jpg Where "xxxxx" is a random number. The filenames are in an Excel file, along with the student's name...

Hi, I don't know if by saying "Sorry, I made a mistake..." that you thought I'd solved the problem. I just made a mistake in stating that I'd bound column 2 in the combo box, not column 1. I've still got the same issue of numbers in my subform and can't figure out why. I've tried some of the...

Sorry, I made a mistake...my bound column in the combo box is 1, and so is looking at the text [DepartmentID]. In the subform, I removed entries in the "Link Child/Master" so as to allow the query to show results. This may have been a low-down and dirty way of doing things, but beforehand, the...

It's my understanding of general database practice that an Autonumber field should be used as a primary key in normalisation tables. I realise my understanding could be wrong, and I'm quite happy to change that practice if need be. I have my normalisation tables. For the most part these...

Can't say I've had the problem before! As Pat has said, splitting the database into backend and frontend systems is a good idea. The way I usually work is to get my tables to 100% percent (I usually make management agree and sign something, so that I can blame them if I argue about later...

The way I'm doing it now is having my normalisation tables set up as say; UID (PK) Department 1 Science 2 Math 3 Arts Any "Department" field in any other tables will be set as text fields, and a form set up to use a combo box to "look up" the data from the...

Here are some screenshots from an Asset Tracking/Call Logging database I'm about 70% through. Note the colour coding. Green = Optional Yellow = Required Red (ish) = Locked Blue = Clickable Link If you want any more information, let me know.

Thanks all for the concise information.

Got it! Changed my bound column to 2 and it works fine. Kind of annoying that Access makes the bound column 1 when using the wizard, despite me saying specifically that I want to use the data from SerialNo field. Grrrr... Thanks for your help.

Thanks, just wanted to be clear on what I should do instead. That's another one off the evil's of the Lookup tab.

Combo box Row Source: SELECT tblMonitors.AssetID, tblMonitors.SerialNo FROM tblMonitors ORDER BY [SerialNo]; Combo box Bound Column: 1 I thought AssetID might be the problem. I'm using the Combo Box Wizard and this is the SQL it gives me. If I edit it to look like this; SELECT...

The criteria is trying to get the value from the combo box. This is the criteria in question. [Forms]![frmMonitorManagement]![cboSerialNo] The field is a text field (in the table). If I remove the above criteria and physically say ="15GTBLAH67", (as an example serial number) it works fine.

Yup, I was referring to the Lookup tab during table design. So, generally what I said is the way to go? Sorry about the double post, I didn't think it posted first time...

I've been using Access for a fair while now, but have only recently come across the community consensus that designing a table with lookups are "bad". Correct me if I'm wrong, but the only real reason I can find for "in table" lookup fields being bad, is that it's an Access only thing, and...

As long as the table structure is 100% finished, there should be no problems with users entering data. If on the other hand, there are likely to be table structure changes, I'd strongly recommend waiting until tables are 100% before entering any live data. Although Colin is right, in some...

I have a table filled with computer monitor information (tblMonitorManagement). I had query that uses combo boxes (cboSerialNo, cboRoom, cboDepartment) on a form for search parameters. The query is called qryMonitorManagement_Sub. The results are displayed in a subform...

I just don't like Access's in built navigation bar. :) If someone happens to want to add another UserType, I want them to be able to see what's already there instantly, and have quick-click access to edit/save/delete. This is the best way, although it will be a rarely used screen. On the...

Erm...creating a listbox with the wizard does this as well I've just discovered (much to my embarassment). Thanks all!

I'll do that if I really have to, but there's only about 6 records, and only ever will be about six records, and I thought it'd be nice to have them all on-screen at the same time. I've got the form so when a record is added, it immediately shows in the listbox, and if a record is deleted it...

I've added this to a command button as suggested; Private Sub cmdFind_Click() DoCmd.FindRecord lbxUserTypeLB End Sub But it results in the following error after selecting something from the listbox; Hitting "Debug" highlights the "DoCmd.FindRecord lbxUserTypeLB" line. I was hoping to...