Search results

You turned off the wizard in the toolbox. Click on the wand thing in the toolbox (looks like a magician's wand with particles coming out of it) to turn the wizards back on. The toolbox works fine. It's just not automating the wizard because that got turned off.

SELECT doesn't work with RunSQL. The error message is just wrong. It's the same as when you have an object open (say, an Excel Object through code), you manually pause the code, and then restart it. You'll get the error "The remote server or host machine cannot be found." It has nothing to...

Access 2.0?! That was the first version of Access I ever used, and that was 1993-1994 or so. Umm, more advice for the boss: "UPGRADE YOUR @#$@#%@! COMPUTER!" Other than that, uninstall Access 2.0 and then reinstall it, but don't use the default path. When it gives you the option, change the...

If you're trying to do this manually, have you just tried the directly through the menus way of it, as in, Tools -> Database Utilities -> Convert Database? That may very well be how you're doing it, but I couldn't tell if you were loading it and then trying to save it or what. Also, make sure...

Are you sure you want to email managers with advice after this? "My advice is to not use SendObject" could not be sent... ;) Anyway, if a mail session could not be started, it usually means that Outlook was not open. I'm 99% sure Outlook has to be open for the SendObject method to work as...

You don't need the actual dates between arrival and departure to be stored anywhere. Just use comparisons. ArrivalDate = #2/20/08# DepartureDate = #2/28/08# If #2/25/08# >= ArrivalDate And #2/25/08# <= DepartureDate Then The mutt is still here Else The owners actually showed back up End If

Option Explicit goes at the top of the code for every module. As already mentioned, it forces variable declaration. To have Access write this line for you, it's in Tools -> Options from the code window. The second checkbox down is Require Variable Declaration. That's the one to check. After...

Straight out of Access Help for RunSQL: That should sound pretty familiar by now. ;)

That's because acViewNormal prints the report by default... Wrong response... That's because conversion requires exclusive access to the DB and you cannot programmatically do it without setting up a separate Workspace (Workspaces(1) in this case) and really, unless you have a boatload of DBs...

Not only does the word normalization scream, I think it aches and begs and says, "Hey, look at me!"

First, let's simplify that so that it isn't so obviously pasted out of a help document: Dim rs As DAO.Recordset Dim x As Integer Set rs = CurrentDb.Open "Select * FROM CNotes WHERE CID = " & Form_PacketClients!RecordID & " ORDER BY NDate DESC, NTime DESC" rs.MoveFirst For x = 1 To 12...

And therefore, the solution is: DoCmd.OpenQuery "Select * from dbo_property" That will, by the way, open the query in datasheet view. If you're trying to open it as a recordset, you'll need to use DAO or ADO.

You'll need to use the IE object. Here's a sample: Dim oIE As InternetExplorer Set oIE = New InternetExplorer With oIE .Visible = True .Navigate "http://www.juno.com" Do Until .ReadyState = READYSTATE_COMPLETE DoEvents Loop...

Something tells me you're using wizards. They make code, and you don't have a lot of control over what they make. Use the wizard to learn, not to program. The code that is automatically produced is usually full of superfluous crap (save a Word Document as an HTML file for example). You need...

DLookup("<fieldname>","<tablename","<optional criteria>") RuralGuy is right. Why didn't you look this up in Access Help?

You have the design backward. As soon as you have more than 255 employees, your table breaks. Put days of the week in columns and employees in rows. Remember, thin and tall (a few columns and lots of rows) is better than fat and skinny (lots of columns and a few rows) in DB design. As for...

If it's imported, then it will act like any other table in Access. Do we have a corruption issue here? Did you compact/repair after the import? What, specifically, is happening?

Finding menu options in ribbons (uses interactive Flash) Finding menu options in ribbons (Excel spreadsheet) A big list of changes, additions, and removals in Access 2007 versus earlier version can be found here.

Don't link the Excel table. Import it. (File -> Get External Data -> Import instead of File -> Get External Data -> Link) Importing makes a table out of it, whereby you can index whatever you want.

Yup, that one just uses a right join instead of a left join. In our example, this is right joining CompanyTable on BattalionTable, including everything from the CompanyTable and only matching records in the BattalionTable. It seems odd that an update would actually perform an append in this...