Search results

It's silly little things like this that should serve as a reminder to everyone why naming conventions are so important. You don't have to use either of these (both very similar), but use something close to it because eventually, someone else is going to have to look at your code. :)...

Doing the spacing (fixed-width or otherwise) sort of defeats the purpose of the listbox if you want to do anything beyond look at the data. Most of the functionality of the listbox disappears (sorting on column 3 for example). If you don't mind the poor man's way around this, set the back...

How do you have the modal form linked to the main form? IF it's on the PK for the Master/Child relationship, it's straightforward. If the form's aren't connected, we have different issues.

Don't use the DoCmd. Do a DCount or a DLookup on the record source (table or query) of the main form. If either DCount or DLookup returns a zero, then the class doesn't exist. If DCount("ClassID","YourTableOrQueryName","ClassID='" & PotentialClassName & "'") = 0 Then ClassName doesn't exist...

Glad it was a simple naming thing. I will suggest not using "Selected" as a field name as that's also a keyword. Make it ItemIsSelected or something as now that I think about it, "IsSelected" is also a keyword in certain situations. At least is wasn't acViewNormal printing your report out or...

Compact/Repair the DB, the zip it and post it.

Is your IsSelected field set to Yes/No or something else? that's the only other parameter in there.

If your cboItemID is alphanumeric (stored as text instead of a number), change it to this: CurrentDb.Execute "UPDATE tblitem SET IsSelected = True WHERE itemID = '" & cboItemID & "'" That would be the missing parameter.

The code I used shown here displays a good use of a collection. Basically, collections are great for holding temporary data when you are not sure how much temporary data you are going to get. Collections will also allow multiple data types, which is a bonus if you're not sure what type(s) of...

How is this a bug? If the current user is an administrator, you won't get an warning message. When testing against all users, it needs to warn. And, if it installs properly, why is a warning message a bug? What breaks or otherwise doesn't work?

Assuming RMA means Return Merchandise Authorization which means an Inventory Control system, you're fishing for something pretty complex. I don't know what you'll turn up, but have you searched for "Inventory Control" or something similar in here or on the Net in general? You'll also want to...

Type the word Collection into the Immediate Window (press Ctrl-G to get that) then highlight it and press F1. A collection is just like an array but easier to manage. For example, if you have an one-dimension array of five entries (0-4), and you delete entry 2, you still have five array...

Text takes single quotes ' Dates take pound signs # Numbers get no qualifiers Therefore: 'MyTextValue' #MyDateValue# MyNumberValue And: SELECT '" & MyTextValue & "'" SELECT #" & MyDateValue & "#" SELECT MyNumberValue As a tip, checkboxes are numeric. -1 equals True and 0 equals False.

The only advantage of the API call is that it doesn't care which version of Access you have. For example, If you write your application in Access 2003 (Office Object Library v11) and an Access 2000 (v10 I think) tries to run it, it will probably fail. If all your users are on the same...

You store the lookup reference to the value, not the value. For example: ID LookupValue 1 Dallas Mavericks 2 Phoenix Suns 3 New Jersey Nets 4 San Antonio Spurs 5 Utah Jazz 6 Boston Celtics You store the number 1-6 multiple times, not the team names.

Well, sheesh. Make a backup DB, test the Import Relationships theory, and give it the old college try. Report back with what you find and pass on information instead of asking for it. That's what this forum is for in the first place.

Unless you set a control for each variable returned, you're SOL here. You could output it all to a memo field in a form, but it depends on what you're trying to do with the data as to how appropriate that might be. Also, Collections are far easier than Arrays to deal with. Just an FYI.

No worries. Glad it was that simple (after all this). And remember, I said in the very first response that I don't like switchboards because they write code for you, and if you don't know coding well, crap like this happens. I'm not accusing you of anything here as it turns out it was...

As promised... Change this: DoCmd.OpenReport "rpttimeclock", acViewNormal To this: DoCmd.OpenReport "rpttimeclock", acViewPreview I'll send a PM with my address for the check. HA! ;) Straight outta (not Compton) but Access Help: Moniker 1, Adam 0. Next.

My bad... forgot there was an actual issue. Give me two minutes for your newb question and I'll humiliate you more. Or not. Or something. :P