Search results

Re: lete a workbook if it exist From Access Sure it works but it is not the proper way to program your code for handling errors. >>> Error Handling In VBA

Re: lete a workbook if it exist From Access I do not recommend using On Error Resume Next. You should test if the file exists, if true, then delete it. If Dir(CurrentProject.Path & "\Peer Review Report.xls" ) <> "" Then Kill CurrentProject.Path & "\Peer Review Report.xls"

It is not recommended to use an access database over a wireless network. The database [and or records opened] can become corrupted is the user loses their signal while in the database and will have to Ctrl Alt Del to kill [close] the database.

The AfterUpdate event of the combo box will do it.

Use the AfterUpdate event of the field that is manually keyed to update the check box.

Instead, try testing if the before value is Nz, if true then do not audit that field for that record.

1) Give the user a filter command to filter out their records based on their ID and also filter a date field. 2) Give the users a Save button to save their changes to the current record 3) Give the users a New Record button to create a new record for them to complete Check out the...

All you want to do is open another database file from a fixed location [C:\yourbackupdatabase.mdb] that never changes with the click of a button, right? If not, what exactly are you trying to do?

Close folder, Close Program Interesting.

Use the application.followhyperlink function. Application.FollowHyperlink "C:\yourbackupdatabase.mdb"

It would be easiest if you bound your form to your table. That way any changes to the current record in the form will be saved to record in the table when your form is bound to your table.

I would change the setup and import the spreadsheet when ever you want to update the table instead of linking to the spreadsheet. You can easily automate the process with the transferspreadsheet command.

When in doubt, google it... http://www.google.com/search?hl=en&source=hp&q=ieinfo5.ocx&aq=f&aqi=g1&aql=&oq=&gs_rfai=CUXOE_A11TOODIZXcygSRiYEGAAAAqgQFT9Dsp8g It is an IE extension. Do you really need it in your database?

Check out the programming for saving, undo and testing if a record is dirty [has been modified but not saved] in my old A Better Mouse Trap? sample which should help your quest.

Re: calander Search the forum for there are calendar demos posted. Access 2007 was kind enough to finally add a built-in calendar control for all date fields.

Bummer! ;-( I am using Access 2007 with Windows XP and Adobe Acrobat 8 Professional.

Are you compacting the database? If you have to archive the data then you might consider moving the records to an archive database if you want to keep the productionn database with only the current data. Moving would involve appending the records from the production database to the arcive...

Use the before update event to verify if the user can save the current record. Check out the programming for saving, undo and testing if a record is dirty [has been modified but not saved] in my old A Better Mouse Trap? sample.

You need to be storing the complete drive\path\file. X:\Drawing\001.pdf

The wizard for creating a subform should walk you through the process. I would question why you need a seperate form to add records and another form to update and delete records. You should be able to do it all with just one form.