Search results

In the control properties, set the TextAlign property to Right

So the error is generated by your CalcUnitPrice function. One possibility is that the type of one of the variables you defined was actually compatible with the values it could take under 97, but not anymore under A2k. Never really heard about such thing pb... Could we see your code?

Between format("#01/04/" & year(date()) & "#") and format("#31/05/" & year(date()) & "#")

Try the following to test if this is a problem related to the ADO references: see if the Date() function returns an error (if so the DAO reference is missing). In module editing view, got to Tools -> References and check if DAO 3.6 or higher is selected as well as ADO 2.1 (or higher). Check that...

How did you happen to have 10 tables about student instead of one? Sound like a desing problem? However if the tables have similar structure (fields), you could try an union query...

Rich is right. If the property allowing contextual menus were set to false you would never get the right-click menu in your DB. So maybe it is that your DB got corrupted somehow (or may one or a few forms). Give a try to Rich's proposal.

right-click does work on most controls that I know, including textboxes, in A2k. If this is an erratic behaviour it is likely to be your mouse. If this is constant, the DB property allowing contextual menus may have been set to 'False'.

MDE have a certain number of limitations in comparison with MDBs, namely (since it is among the purposes of making an MDE) that the DB is not modifiable anymore (no new query, etc). Indeed, you will want to make backup of your MDB , then create an MDE and test how it is running to detect...

You can for example use a macro called autoexample, with two lines: SelectDBObject (you have to check the parameter saying that the object is in the DB window, I think it must be 'True') HideDatabaseWindow I may not be perfectly correct regarding the names of these two macro functions, since I...

Yes Yes There is also a menu item called re-link tables (or is it linked tables manager...?)

Most frequent cause to my knowledge are indeed users shutting the DB improperly (Ctrl+Alt+Del, switch off button, etc...). As to repairing, the downalodable MS 'JetComp' is a great asset. Get it from the MS site. But of course you must look after preventing corruption in first instance.

You are loking after the common dialog control, or preferably to my opinion (the CDP may lead you to distribution and references problem) APIs: http://www.mvps.org/access/api/api0001.htm Dev Ashish's website is a huge mine of info and tips on Access...

An 'ASP and ASP.NET' forum definitely has my vote too!

Any idea where the error happens?

I have a small DB that generates all VBA and Access error codes with there descriptions. Provide your email if interested. As to your question, it is all in twisting Rich's ears. Right one provides MSDN articles IDs, left one VBA + Access error numbers. :p Don't dream too much about developping...

Sorry, these options do exist for A2K and above. No other idea than having your own search button opening the search dialog in the mode you want, programatically... Well... twisted Rich's ear and this is what I got: Article ID Q120912 The 'solution' uses Sendkeys though...:D...

Tools>Options> Edit/Find Tab

Field: [EmployeeStartDate] Criteria: Between DateAdd("d",83,[forms]![frm-90dayreviewtime]![meetingdate]) and DateAdd("d",90,[forms]![frm-90dayreviewtime]![meetingdate]) Possibly you may have to replace comas with semi-colons

Ex: assuming that you want to update the field Name in Voters from Name in Import where records have the same ID1 UPDATE Import INNER JOIN Voters ON Import.ID1 = Voters.ID1 SET Voters.Name = Import.Name;

In most cases the most efficient is to gather all the info you need in your queries , and avoid calculations in queries (in particular the ones using functions, have the calculations done in your reports as far as possible)