Search results for query: *

Just found and used the Microsoft tool at http://www.microsoft.com/security/malwareremove/default.mspx to do a full system scan: no malicious software found (only of the list it tests for, of course). Plan to use these pages, although I may have already done most of what's on them...

What about changing the recordsource based on the combo's value and then requerying the subform?

The decompile went smoothly; I compacted two more times, but the problem remains.

Yes, I've done that a number of times and just now, too. Is there any malware or other such garbage on the market that could bring this about, or can malicious code be made such that "if user x navigates to records y or z, or uses first record navigation buttons, quit app"?

Without a more standardized way of receiving the data, you're probably better off correcting it through update queries rather than instructing Access to impute equivalents. You could make queries like the following: "Update Table set Location = 'Standard Name' where Location in ('Name...

I updated Office but the problem remains. Anyone have any more thoughts on this, or has anyone ever encountered or heard of this before? I'm particularly interested in finding out if this can be brought about intentionally by someone with access to the Office software kept on the network. Can...

Just did a Detect and Repair to no avail; am now checking for updates at Microsoft.com.

Thank you both for these posts. I did reinstall Office from our network, but unfortunately have no access to Office CD's and no control over what is kept on the network to draw from. When I check "About..." it says (Access 2002) SP3. Interestingly, whenever I use the wizard to create a look...

I've been experiencing total Access shutdowns in response to routine record navigation with a form. They nearly always occur in response to: clicking the first-record navigation arrow in the lower left area of form view; clicking the first-record navigation button created on the form using the...

This thread may be able to change your life: thread705-1192709.

Wow - even lars7 updated to the thread while I was still writing the one above :-).

Looks like PHV's post updated to the thread while I was still editing this one.

Well, it does seem like you're likely looking for just "WHERE Code IN (" & strCode & ") And datetopayroll is null", but only as long as every record 'currently' containing the right code number(s) that also happens to have a blank datetopayroll field truly is available for this immediate use...

Excellent link from bubba100, leads to even more. Thanks.

I'm glad I found this thread. I'm having success with this modified version: SD = Format(SD, "medium date") ED = Format(ED, "medium Date") xl = "H:\1\" & SD & " to " & ED & ".xls" DoCmd.TransferSpreadsheet acExport, 8, "Excel Report Query", xl, True, "" Dim strPath, objXL strPath = xl...

The "Dim's": Dim oapp As Word.Application Dim oword As Word.Document You may need this inside the If/Then, too: ActiveDocument.MailMerge.OpenDataSource "Path&FileName", , , 0, -1, , , , , , , , "", "", 0

How about something like: Set oApp = CreateObject("Word.Application") Set oWord = oApp.Documents.Open(FileName:="C:\File.doc") oApp.Visible = True If ActiveDocument.MailMerge.State = wdMainAndDataSource Then ActiveDocument.MailMerge.Execute End If

Ok, the answer is: Create an export spec in which you blank out the Time Delimiter field. Then add it to the code: DoCmd.TransferText acExportMerge, "SpecName", "QueryName", "C:\Folder\FileName.txt", True, "" Interestingly, you can't get the text export wizard to appear in order to make the...

Has Word been opening up showing just a dark grey blank area instead of your document?

When I transfer text from a query to a .txt file through VBA or a Macro, date fields include the unwanted 00:00:00 time element, i.e., “01/18/2006 00:00:00.” I need to eliminate this so it doesn’t show up in merge docs that use the output for data. Why is it that when I export the same query...