Search results

You'll need Office Developer Edition or Access Developer Extensions. The alternative is to redevelop the app using VB - which would be more expensive than using the first option

Please ensure that your References include the DAO library

Here's a sample that I have posted that shows how this is done http://www.access-programmers.co.uk/forums/showthread.php?t=111241

You should try to compile the application, i.e. go into any module then Debug->Compile and see if any errors show up

also, what version of Access are you using?

also, what version of Access are you using?

Good morning Can you send me the file..I'll see what's going on with this. My email address is STCYRM@AOL.COM

Normally the DBF file format should follow the DOS naming convention, ie. the name is 8 letters with the .DBF extension

The sample database that I posted a while back might be of some help to you. http://www.access-programmers.co.uk/forums/showthread.php?t=108698

As mentioned in the other posts, you should rethink your design

Hi I've posted a sample database that does just that. It's available at: http://www.access-programmers.co.uk/forums/showthread.php?t=103456

Check the Sample Database area, there's an example there

Don't forget that you have to set the Limit To List to YES

You don't need to modify your table. Simply create a query and do your calculations there

In this case, with the use of 2 listboxes you could possibly use the sample that I posted before: http://www.access-programmers.co.uk/forums/showthread.php?t=107665 where you could modify this sample as per the MoveRecord sample.

Here's a function that may be useful Function fCardinalDate(bytDay As Byte) As String Select Case bytDay Case 1, 21, 31 fCardinalDate = bytDay & "st" Case 2, 22 fCardinalDate = bytDay & "nd" Case 3, 23 fCardinalDate = bytDay &...

Is the new field part of your Recordsource for your report?

Hi Look at the Movesize command

Outlook Style Interface here's a screenshot of an Outlook Style interface that I use in some applications

Maybe you should try the following for starters: 1) repair / compact the current database 2) create a new blank database and import all of the objects from the "bad" database into the new one.