Search results

Tools>Options>Advanced>Default File Format - change to Access 2003

Like I said I had to edit it to capture null value changes Here is the code I use:- Sub AuditTrail2(frm As Form, RecordID As Control) 'Track changes to data. 'recordid identifies the pk field's corresponding 'control in frm, in order to id record. Dim ctl As Control Dim varBefore As...

If you base your report on a parameter query then you will be prompted to enter the parameters when the report is produced, just as you would when running the query. To hide the Database window in A2000 you go to Tools>Startup and uncheck the Display Database window option. Feel free to ask...

I use the audit trail in this link and think it could be what you're after:- http://articles.techrepublic.com.com...1-6166807.html I have had to edit it to ensuring null value changes are captured (null to value & value to null)

Then hide the Database window and distribute an .mde file - http://eu.dummies.com/WileyCDA/how-to/content/securing-your-access-2003-database-as-an-mde-file.html And what happens when you run that query directly? Do you still get prompted to enter parameters?

What happens when you run the query directly?

The only problem with linking the Spreadsheet is that if the Linked Spreadsheet is being used in Access (eg as control source in a form that is open) then you are unable to open the Spreadsheet...

Another tip I was given was to create a form based on a small, simple table and open this form in hidden mode in an autoexec macro. This form then stays open in the background ensuring connection with the back end is constant. This, along with the unchecking of Name Autocorrect, has made my...

Is it the same Excel file to be used every time? If so, why can the data not be imported into the existing table? What changes in the Spreadsheet? New records? Updates to existing records? You are proposing to create a new table and query every day - pretty soon your DB will become...

Would I be correct in assuming that the text box is unbound?

I think he wants to import an Excel attachment from an Outlook email...

More info needed here. Is the Spreadsheet to be imported into a new or existing table? If it is an existing table (or even imported into a new table and then appended into an existing table) then there should be no need to edit any joins in an existing query. What other steps are...

Try = Null rather than Is Null. I wouldn't put this behind a command button (unless its a custom save button) as this relies on the user to click the button which is not something you want to be doing...

In which event are you performing the check? You wouldn't want to perform it in either controls after update event so I would think the logical place to check would be in the forms before update event. The logic in your code is also out. Try:- If Me.txtSe = Me.ReSNum Then Me.txtSe Is Null...

Do you get this message when you perform the import? "The first row contains some data that can't be used for valid Access field names. In these cases, the wizard will automatically assign valid field names." If you do then the reason your column is being named 'Field13' is because the field...

Yes - on the buttons on click event use the following code:- Dim pResponse As String Dim lSalesPersonID As Long Dim lEditHwnd As Long Dim lTemp As Long Dim sPwd As String gMsgTitle = "Security Check" gMsgType = vbOKOnly + vbInformation gMsgText = "Enter Password" Beep...

In the after update event of the combo box, something along the lines of:- If Me.YourComboBoxNameHere = "YourValueToShowHiddenControlHere" Then Me.YourHiddenControlNameHere.Visible = True Else Me.YourHiddenControlNameHere.Visible = False End If How are you hiding the control? I would...

Wrap this around your code:- If Me.YourCheckBoxNameHere = 0 Then 'the rest of your code here End If

I am guessing that you are using Access & Outlook 2007? This error message is probably the result of tighter security for Outlook 2003 onwards(?) In A2000 you can get around this by installing CDO and sending directly from your SMTP server bypassing Outlook completely, this might also work...

the .Fields(0) part