Search results

Yes, but without sharing the possible pitfalls to that suggestion is why I chimed in and stated thusly.

In my opinion that is a bad thing to do. You should not use lookups at table level unless you are very, very experienced and know of all of the pitfalls of doing so.

Re: MS Access/JET "Join Expression Not Supported" Any Way to Fix This Query? It is LEFT JOIN, not LEFT OUTER JOIN.

You can if you build your own form instead of relying on parameter prompts.

1. Use the After Update event of the combo box not the Change event. 2. put a message box into the code to return the value of the cboSpecies so you can see if it is returning what you think it should be returning.

How about this: =IIf(Len([MasterCasemaxUnits] & "") = 0,[MasterCaseMinUnits],[MasterCaseMinUnits] & " - " & [MasterCaseMaxUnits])

Fair enough. So the way to do it would be to do it similar to what Chris wrote here: http://www.access-programmers.co.uk/forums/showpost.php?p=1255765&postcount=9

So you aren't wanting to just have the LIMIT TO LIST property set to YES and then don't allow new values? It is easier.

Do you have the periods in the numbering? If so, get rid of them. Line numbers don't have periods. Also is the Visual Basic: actually in the code? That should not be there.

It may seem easier up front, but it will cause you no end of grief when you want to get data out. Do it the way plog said. And, that being said, you will want to make sure your data is normalized so you may not be having all the fields you envision in the same table. And, as for...

It is still opening it behind the scenes. You can't get something out of something without it technically being opened.

Even if only one person uses the database, it should be split and each person given a copy of the frontend. Your odds of corruption are greatly increased if it isn't split, hence potential loss of data. Plus if it is split and someone's frontend corrupts the others can keep working while you...

You would need to build the SQL in VBA to do this. Do you want to go there? If so, I'll post code to do it.

See if you can incorporate elements of this into it: http://www.freevbcode.com/ShowCode.asp?ID=562

Create a macro called AutoKeys and then in the Macro Name you would use ^+I as its value and under Action use RUN CODE and put in the procedure name with the parens in its FUNCTION NAME argument near the bottom of the screen. In 2007 I've noticed that Sub doesn't always work but Function...

What code do you use to open the database?

I don't have 2010 at work but will try to remember to look when I'm at home later tonight, unless someone else who has 2010 cares to look and respond, which is quite alright.

How are you trying to open the database? The reason I ask is that I believe we need to modify that because hitting Cancel will not open the database anyway so why try if you can't open it? So what are you currently using to open it?

Okay, so first off, you should rename your controls to something meaningful instead of Combo13, etc. BEFORE adding any code as it will then have to be moved to the new name/event. But I would rename them ASAP as it also helps to understand just by looking at the name what it is. For example...

Just for clarification, it is ADDITIONAL to the two events I already gave you. What the .Visible is looking for is a True or False and so the part after the = sign that I wrote will generate either a True or a False. vbNullstring is actually the constant for "" which is an EMPTY STRING, not a...