Page 323 of 951« First...102030...321322323324325...330340350...Last »

ENT2001: Attempt to Send an E-mail Message Generates Error 5550

When you attempt to send an e-mail message, you may receive an error message that cites Error 5550 and states that your e-mail cannot be sent because of Simple Mail Transport Protocol (SMTP) relay blocking.
This error can be the result of any of the following e-mail configurations:

  • You are logged on to a local area network (LAN) that has an Internet gateway, and you attempt to send e-mail through the Internet Service Provider (ISP) SMTP gateway.
  • You are logged on to an ISP, and you attempt to send e-mail through another ISP’s SMTP gateway.
  • You are using a cable modem or an Asymmetric Digital Subscriber Line (ADSL) to get to another ISP, and you attempt to send e-mail through that ISP’s SMTP gateway.
    Note that this issue affects all messaging clients, regardless of the manufacturer.
Because this issue is not caused by the e-mail client, you must contact your ISP for information about how to resolve the issue. There is currently no known resolution of the issue if an ISP blocks all SMTP relay traffic.

Most of the new software for SMTP e-mail gateways allows relay for specific IP addresses. Cable modem or ADSL providers must provide a static IP address for the customer; the customer’s e-mail ISP allows relaying for that specific IP address. Banks of IP addresses can also be allowed, which can provide a workaround for some corporate customers who access ISPs through the corporate LAN.

If the error occurs randomly, your SMTP server may be checking to verify that the domain or the recipient name actually exists before sending the message. If the recipient’s mail server is temporarily unavailable for some reason, such as high network volume, your SMTP server cannot verify the address and may reject the relay. In this case, no action is required. The message is sent when the receiving server is again available.

Article ID: 299916 – Last Review: November 2, 2013 – Revision: 2.0


Applies to
  • Microsoft Entourage 2001 for Mac Special Edition
kbnosurvey kbarchive kberrmsg kbnetwork kbprb KB299916

See the original article here:
ENT2001: Attempt to Send an E-mail Message Generates Error 5550

Microsoft Access: How to Group Column Headings in a Crosstab Query

This article describes how to group values in a crosstab query by using a
fixed number of headings, rather than by having a column for every value.

NOTE: You can see a demonstration of the technique that is used in this article in the sample file Qrysmp00.exe. For information about how to obtain this sample file, please see the following article in the Microsoft
Knowledge Base:

207626

(http://support.microsoft.com/kb/207626/EN-US/
)

ACC2000: Access 2000 Sample Queries Available in Download Center

The following example demonstrates how to use the Switch() function to group non-numeric values under four fixed headings. The headings are
“A-F,” “G-O,” “P-Z,” and “Other.”

CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.

  1. Start Microsoft Access and open the sample database Northwind.mdb.
  2. In the Database window, click Queries, and then click New to create a new query.
  3. In the New Query box, click Design view, and then click OK.
  4. In the Show Table dialog box, add the Customers table and the Orders table to the query grid by double-clicking on Customers, double-clicking on Orders, and then clicking Close.
  5. On the View menu, click Totals to display the Totals row in the grid.
  6. On the Query menu, click Crosstab Query to display the Crosstab row in the grid.
  7. Complete the query grid, using the following specifications:

    NOTE: In the following sample expressions, an underscore (_) at the end of a line is used as a line-continuation character. Remove the underscore from the end of the line when re-creating these expressions.

       Field: Country
          Table: Customers
          Total: Group By
          Crosstab: Row Heading
       Field: Expr1: Switch(CompanyName Like "A-Fa-f*", "A-F", _
                     CompanyName Like "G-Og-o*", "G-O", CompanyName_
                     Like "P-Zp-z*", "P-Z", True, "Other")
          Total: Group By
          Crosstab: Column Heading
       Field: OrderID
          Table: Orders
          Total: Count
          Crosstab: Value
    						

    Note that both “A-F” and “a-f” are required in the Switch() function’s argument because the argument is case-sensitive. The “True” in the argument acts like an Else condition, collecting data that does not match any of the previous conditions.

  8. Run the query.
For more information about crosstab queries, click Microsoft Access Help on the
Help menu, type create a crosstab report with fixed-column headings in the Office Assistant or
the Answer Wizard, and then click Search to view the topics
returned.

For more information about the switch function, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type switch function example in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

Article ID: 209141 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Access 2000 Standard Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Office Access 2003
  • Microsoft Office Access 2007
  • Microsoft Access 2010
kbnosurvey kbarchive kbhowto kbinfo KB209141

Read More:
Microsoft Access: How to Group Column Headings in a Crosstab Query

XL2001: Copying Sheets May Cause Macro Alert to Appear

If you copy a worksheet, you may receive the following warning:

The workbook you are opening contains macros.

Some macros may contain viruses that could be harmful to your computer.

You receive the warning as if you were opening a workbook with macros, although you are not.

This problem can occur when the following conditions are true:

To work around this problem, review the cause and pick the method below most appropriate to the cause and your needs.

NOTE: Microsoft recommends that you do not turn off Macro Virus Protection to resolve this problem. If sheets are copied into a new workbook or a workbook that contains no macros and the file is saved, you will not receive the warning.

If you need the macro code and button, see the “Move the Code” section of this article.

Method 1: Delete Button Reference, Button, Macro Definition, Macro Sheet or Code

If you have an XL4 type macro sheet in the workbook, you can resolve the problem by removing the macro definitions, and deleting all macro sheets. If a button has referred to the XL4 type macro, you also need to remove the reference to that macro from the button or remove the button. All three are needed to resolve the problem.

If you have Visual Basic for Applications macro code, you can resolve the problem by removing the reference to that macro from the button, or removing the button.

Choose the appropriate methods from the following.

Method 1A: Delete Button Reference

Remove the button reference by using the following steps:

  1. With the CONTROL key pressed, click the button or object, and click Assign Macro on the shortcut menu.
  2. In the Macro name edit box, with the name of the macro highlighted, click the DELETE key.
  3. With the Macro name edit box clear, click OK.
    NOTE: Visual Basic for Applications macro code without the button reference should not cause the problem.

Method 1B: Delete the Button

If you do not need or want the button, you can delete the button. To do this, follow these steps:

  1. With the CONTROL key pressed, click the button or object to select it.
  2. On the Edit menu click Clear and All.

Method 1C: Delete the Macro Definition

With macro sheets, remove the macro definition. To do this, follow these steps:

  1. On the Insert menu click Name and then click Define.
  2. For each name in the workbook that defines a macro, select it and click Delete.
  3. Click OK to close the dialog box.NOTE: If you have XL4 type macro sheets, to resolve this problem, you must remove the macro definitions, delete all macro sheets, and delete any reference to a macro in a button or object.

Method 1D: Delete XL4 Macro Sheet

If you need the macro code, see the “Move the Code” section.

  1. Click the tab of the macro sheet.
  2. On the Edit menu, click Delete Sheet.

    You receive the following warning:

    The selected sheet(s) will be permanently deleted.

  3. Click OK.

Delete Visual Basic for Applications Macro Code or Module

Although it is not necessary to remove Visual Basic for Applications macro code or modules to resolve this problem, you can remove Visual Basic for Applications code. To do this, follow these steps:

  1. On the Tools menu, click Macro, and then click Visual Basic Editor (or press OPTION+F11 on some systems) to start the Visual Basic Editor.
  2. Find the Project – VBA Project window. If it is not visible, click Project Explorer on the View menu.
  3. In the Project – VBA Project window select the workbook project with the code and click the triangle on the left to turn it down and view the objects and modules in the project.
  4. Click on the triangle on the left of the Modules folder to turn it down and show individual modules.
  5. Double-click on a module to view the code in a code window. If you want to remove the code, highlight all of the code in a subroutine and press DELETE to remove it.
  6. If you want to remove the whole module, click the File menu and select Remove Module (listed by module name such as “Module1″), and when prompted, click Yes to delete the module.
  7. Do this with all modules in which you want to clear the code or remove the module.
  8. When you are finished, on the File menu click Close and Return to Microsoft Excel and then save the file.

Method 2: Move the Code

If you need the code and/or button and want to avoid the problem by moving the code or macro sheet to a different workbook, use the most appropriate of the following methods.

Method 2A: Move Macro Sheet to a Different Workbook

If the problem is caused by macro code in a Macro sheet, move the Macro sheet to another workbook. Redefine the macro in that workbook, and remove the macro definition in the current workbook.

For additional information about steps to move a macro sheet, click the article number below
to view the article in the Microsoft Knowledge Base:

288400

(http://support.microsoft.com/kb/288400/EN-US/
)

MacXL: How To Move Macro Sheet to Another Workbook

If you have buttons or objects assigned to the run macro code, reassign them to run the code in the new location.

Method 2B: Move Module Code to a Different Workbook

If the problem is caused by a button or object assigned to run Visual Basic for Applications macro code in modules, follow these steps:

  1. Move the code referred to by the button or object to another workbook.
  2. Reassign the button or object to run the code in the new location.

For additional information about steps to move module code, click the article number below
to view the article in the Microsoft Knowledge Base:

288401

(http://support.microsoft.com/kb/288401/EN-US/
)

Excel: How To Move Module Code to Another Workbook

Method 3: Use Visual Basic Code

Because Visual Basic code does not cause this warning, create Visual Basic for Applications macro code in a different workbook to copy sheets in the active workbook.

For additional information about copying sheets with code, click the article number below
to view the article in the Microsoft Knowledge Base:

288402

(http://support.microsoft.com/kb/288402/EN-US/
)

MacXL: How To Copy or Move Sheets by Using VBA Code

NOTE: The code needs to be in a separate workbook. This is because of a problem in Excel 2001 when the Visual Basic for Applications code that is used to copy sheets is in the same workbook as the sheets being copied.

For additional information about the problem copying worksheets with code in the same workbook, click the article number below
to view the article in the Microsoft Knowledge Base:

286266

(http://support.microsoft.com/kb/286266/EN-US/
)

XL2001: Excel Hangs When You Copy Worksheet in Same Workbook

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
When you get the macro warning, if you click Disable Macros you may get a second warning that says:

This workbook contains a type of macro (Microsoft Excel version 4.0 macro) that cannot be disabled. There may be viruses in these macros.

If you click Enable in the first warning or click Yes in the 2nd warning, the copy is made. If you click No in the second warning, no copy is made.

For more information about copying worksheets, follow these steps:
  1. On the Help menu, click Contents and Index, click Index, and then click C.
  2. Scroll down until you locate copy, and then click the arrow to the left to view a list of topics under the general topic.
  3. Click Move or copy sheets.

If you cannot find the information that you want, ask the Office Assistant.

For more information about Macro Viruses, follow these steps:

  1. On the Help menu, click Contents and Index, click Index, and then click M.
  2. Scroll down until you locate macro, and then click the arrow to the left to view a list of topics under the general topic.
  3. Click About viruses and workbook macros.

If you cannot find the information that you want, ask the Office Assistant.

For more information about Macro virus protection, follow these steps:

  1. On the Help menu, click Contents and Index, click Index, and then click M.
  2. Scroll down until you locate macro, and then click the arrow to the left to view a list of topics under the general topic.
  3. Click Check workbooks for macro viruses.

If you cannot find the information that you want, ask the Office Assistant.

Article ID: 286265 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Excel 2001 for Mac
kbnosurvey kbarchive kbbug kbdtacode kbpending KB286265

See the original article here:
XL2001: Copying Sheets May Cause Macro Alert to Appear

ACC2002: How to Use the Find Unmatched Query Wizard

You can use the Find Unmatched Query Wizard to create a select query that finds records in one table that do not have related records in another table.

For example, in the Northwind.mdb sample database, you can find customers who do not have orders. The query compares the Customer ID field in the Customers table with the Customer ID field in the Orders table. The query finds all instances of Customer ID entries that appear in the Customers table but that do not appear in the Orders table.

If the Enforce Referential Integrity feature has been selected, a Customer ID cannot exist in the Orders table (on the “many” side of the relationship) unless it exists in the Customers table (on the “one” side of the relationship). A company that has not placed an order can be listed as a customer, but each order must have a customer.

To use the Find Unmatched Query Wizard, follow these steps.

CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.

  1. Open the Northwind.mdb sample database.
  2. In the Database window, click Queries under Objects, and then click New on the Database window toolbar.
  3. In the New Query dialog box, click Find Unmatched Query Wizard, and then click OK.
  4. In step 1 of the wizard, click Table: Customers in the list of tables and queries, and then click Next.

    NOTE: The Customers table contains the records that you want in the query results.

  5. In step 2 of the wizard, click Table: Orders in the list of tables and queries, and then click Next.
  6. In step 3 of the wizard, click CustomerID under Fields in ‘Customers’.

    Under Fields in ‘Orders’, click CustomerID, and then click the <=> button to designate these fields as the ones to be compared. Click Next.

    NOTE: Access selects the CustomerID fields because they have the same name. However, fields that match might have different names.

  7. In step 4 of the wizard, select the files that you want to include in your results. For this example, click the Add All Fields (>>) button, and then click Next.
  8. In the final step of the wizard, change the title of your query. For this example, accept the default name Customers Without Matching Orders, and then click Finish.

    The query returns two records.

NOTE: If the resulting query is not exactly what you want, you can rerun the wizard or change the query in Design view.

For additional information about how to enforce referential integrity, click the article number below
to view the article in the Microsoft Knowledge Base:

304466

(http://support.microsoft.com/kb/304466/EN-US/
)

ACC2002: Defining Relationships Between Tables in a Microsoft Access Database

Article ID: 319017 – Last Review: November 2, 2013 – Revision: 4.0


Applies to
  • Microsoft Access 2002 Standard Edition
kbnosurvey kbarchive kbhowto KB319017

See more here:
ACC2002: How to Use the Find Unmatched Query Wizard

ACC2000: GoToControl to Control with Focus in AfterUpdate Ignored

You you try to use the GoToControl method or the SetFocus method in the AfterUpdate event of a control to set focus back the control that is being updated, the GoToControl or SetFocus method will be ignored. For example, the following code, will not cause the control named MyControl to retain focus once it is updated:

Private Sub MyControl_AfterUpdate()
   DoCmd.GoToControl "MyControl"
End Sub
				

You will see the same behavior when you use the GoToControl action in a Macro.

You cannot set the focus on a form to an object that already has focus.
You can get the desired results in one of the following ways:

  • To stop the control focus from changing, regardless of the update status of the control, set Cancel = True in the Exit event of the control.
  • If you want to prevent the changed data from being saved, set Cancel = True in the BeforeUpdate event of the control.

The following example maintains focus on a control, regardless of the update status of that control:

Private Sub MyControl_OnExit(Cancel As Integer)

   Cancel = True

End Sub
				

When you add this code to a control, the only way to move to a different control on the form is by using the pointer.

For more information about the GoToControl action, click Microsoft Access Help on the
Help menu, type GoToControl in the Office Assistant or
the Answer Wizard, and then click Search to view the topics
returned.

For more information about the GoToControl method, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type GoToControl method in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

Article ID: 208178 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbprb kbusage KB208178

Continue Reading:
ACC2000: GoToControl to Control with Focus in AfterUpdate Ignored

ACC2000: How to Print a Blank Line Every Nth Line in a Report

This article was previously published under Q208696

This article has been archived. It is offered “as is” and will no longer be updated.

Moderate: Requires basic macro, coding, and interoperability skills.

This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).

This article shows you how to add blank lines between the printed lines on
a report. You can use this method to add a blank line after a set number of
lines. For example, you could use this method to add a blank line after
every five lines of data in your report.

NOTE: This article explains a technique demonstrated in the sample
file, RptSmp00.mdb. For information about how to obtain this sample file,
please see the following article in the Microsoft Knowledge Base:

231851

(http://support.microsoft.com/kb/231851/EN-US/
)

ACC2000: Microsoft Access 2000 Sample Reports Available in Download Center

CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.

To add a blank line after every five lines in a report, follow these steps:

  1. Open the sample database Northwind.mdb.
  2. In the Database Window, click Reports under Objects, and then click New.
  3. In the New Report dialog box, click Report Wizard, select the Employees Table, and then click OK.
  4. In the Available Fields box, select EmployeeID, and then click
    the > button. Repeat this step for the LastName, FirstName, and
    BirthDate fields, and then click Next.
  5. Select BirthDate as the primary group level, click the > button, and then click Next.
  6. Select LastName as the field to establish sort order in Field 1, and
    then click Next.
  7. On the How would you like to lay out your report? screen, click Next.
  8. On the What style would you like? screen, click Next.
  9. On the What title would you like for your report? screen, type
    Employee Birthdays, and then click Finish.
  10. View the new report in Design view.
  11. On the View menu, click Code.
  12. Type the following lines in the module’s Declarations section:
    Option Compare Database
    Option Explicit
    ' This code declares the cLines variable as an integer, and the
    ' cMaxLine constant as five. You can set the cMaxLine constant
    ' to insert a blank line after as many lines as you want. For
    ' example, to add a blank line after every eight lines in the
    ' report, set cMaxLine=8.
    Dim cLines As Integer
    Const cMaxLine=5
    					

  13. In the Object box of the code module, select Report. In the Procedure box of the code module, select Open. Type the following procedure:
    Private Sub Report_Open (Cancel As Integer)
       'This code initializes the cLines variable to zero.
       cLines = 0
    End Sub
    					

  14. In the Object box, select Detail. The Procedure box will change to Format. Type the following procedure:
    Private Sub Detail_Format (Cancel As Integer, FormatCount As _
                  Integer)
       ' This code adds a blank line by setting the NextRecord and
       ' PrintSection properties.
       If cLines Mod (cMaxLine+1) = 0 Then
          Me.NextRecord = False
          Me.PrintSection = False
       End If
       cLines = cLines + 1
    End Sub
    					

  15. Close the module, and then preview the report. Note that there is a
    blank line in the report after every five lines of detail.
For more information about the NextRecord property, click Microsoft Access Help on the
Help menu, type NextRecord property in the Office Assistant or
the Answer Wizard, and then click Search to view the topics
returned.

For more information about the PrintSection property, click Microsoft Access Help on the
Help menu, type PrintSection property in the Office Assistant or
the Answer Wizard, and then click Search to view the topics
returned.

Article ID: 208696 – Last Review: November 2, 2013 – Revision: 2.0


Applies to
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbdta kbhowto KB208696

Follow this link:
ACC2000: How to Print a Blank Line Every Nth Line in a Report

MOD2000: Access Run-Time Minimum Is Not Updated by Office 2000 SR-1

This article was previously published under Q265079

This article has been archived. It is offered “as is” and will no longer be updated.

After you install Microsoft Office 2000 SR-1 on a computer that has the Access Run-Time installed, you notice that the Access run-time files have not been updated.
You have a copy of Access Run-Time Minimum installed on the computer.
Even though full Access Run-Time can be updated by Microsoft Office 2000 SR-1, Access Run-Time Minimum cannot be updated.
If you create a new package with Access 2000 SR-1 Run-Time and redistribute it with the same database and package name, the Access database on each user’s computer will be overwritten. Also, if Access 2000 Run-Time Minimum is already on the computer, Access 2000 SR-1 Run-Time is not installed. For these reasons, it is recommended you use the method described below.

On each computer, remove the Access Run-Time Minimum program, and then install Access 2000 SR-1 Run-Time, as detailed in the following steps:

  1. Order the Microsoft Office 2000 Developer Service Release 1 fulfillment CD.

    NOTE: Access 2000 SR-1 Run-Time is only available on the fulfillment CD and is not part of the Microsoft Office 2000 Developer Service Release 1 download from Microsoft.For additional information about Microsoft Office 2000 Developer Service Release 1 and how to order the fulfillment CD, click the article number below
    to view the article in the Microsoft Knowledge Base:

    253566

    (http://support.microsoft.com/kb/253566/EN-US/
    )

    MOD2000: How to Obtain and Install Microsoft Office 2000 Developer Service Release 1 (SR-1)

  2. At each computer that has the solution installed, on the Start menu, point to Settings, and then click Control Panel.
  3. In Control Panel, double-click Add/Remove Programs.
  4. Click Microsoft Access 2000 Runtime, and then click Add/Remove. If you are running Microsoft Windows 2000, click Change/Remove.
  5. On the Access Runtime Setup screen, click Remove Microsoft Access 2000 Runtime. When prompted if you are sure, click Yes.

    NOTE: By doing it this way, you only remove Access 2000 Run-Time Minimum and not your application data or shortcut.

  6. Install Access 2000 SR-1 Run-Time either from the fulfillment CD or from a network share. Make sure to install it in the same folder where Access 2000 Run-Time Minimum was installed.

Steps to Reproduce the Behavior

  1. Package an Access run-time solution with Access 2000 Run-Time Minimum.
  2. Install the package on another computer that has only Microsoft Word 2000 installed and no version of Access installed.
  3. On the Start menu, click Search or Find, and search for MSAccess.exe.
  4. When it is found, right-click the file, and then click Properties on the shortcut menu. Make note of the size, version, and date of MSAccess.exe.
  5. On the Start menu, click Search or Find, and search for WinWord.exe.
  6. When it is found, right-click the file, and then click Properties on the shortcut menu. Make note of the size, version, and date of WinWord.exe.
  7. Install Microsoft Office 2000 Service Release 1 (SR-1).
  8. On the Start menu, click Search or Find, and search for MSAccess.exe.
  9. When it is found, right-click the file, and then click Properties on the shortcut menu. Note that the properties you took note of earlier have not changed. Access was not updated.
  10. On the Start menu, click Search or Find, and search for WinWord.exe.
  11. When it is found, right-click the file, and then click Properties on the shortcut menu. Note that none of the properties you took note of earlier have changed. Word was updated.
For additional information about a similar issue involving an Access run-time application and SR-1, click the article number below
to view the article in the Microsoft Knowledge Base:

275253

(http://support.microsoft.com/kb/275253/EN-US/
)

MOD2000: Unable to Install Microsoft Office 2000 Service Release 1 (SR-1/SR-1a) Update onto a Computer That Has a Run-Time Application

Article ID: 265079 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Office 2000 Developer Edition
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbpdwizard kbprb KB265079

More:
MOD2000: Access Run-Time Minimum Is Not Updated by Office 2000 SR-1

Lotus Macros That Do Not Directly Translate into Excel

The following is a list of Lotus 1-2-3 macro commands that do not have
direct equivalents in Microsoft Excel. These commands either cannot be
translated to Microsoft Excel commands when you use the Macro Translation
Assistant or they will require extensive editing in Lotus before you are
able to translate them properly.

Things to Look for When You Edit Macros in Lotus

WYSIWYG commands:

Microsoft Excel doesn’t recognize the add-ins that provide WYSIWYG
capability (such as Allways and Impress). These commands are preceded by a
colon (:) character in the macro.

Macros that reference another sheet in a workbook:

Later versions of Lotus 1-2-3 use multiple sheets, but Release 2.01 is a
single-sheet program. Because the Microsoft Excel Macro Interpreter only
recognizes macros compatible with Release 2.01 of Lotus 1-2-3, macros that
reference another sheet will fail. To identify commands that reference
another sheet, look for a sheet name followed by a colon (for example
“A:a1″).

Names longer than a single letter:

Lotus 1-2-3 macros in Release 2.01 must be named “” where
is a single letter. Later versions of Lotus 1-2-3 allow macros with longer
names, but they cannot be run in Microsoft Excel.

Macros that do not work through the Macro Interpreter will not work any
better if they are translated using the Macro Translation Assistant.

Microsoft Excel version 4.0 Help, Search, Lotus 1-2-3, Overview of Macro
Translation Assistant

Microsoft Excel version 3.0 Help, Index, Switching from Lotus 1-2-3, Macro
Translation Assistant, Lotus 1-2-3 Commands that Require Editing to
Translate

Microsoft Excel version 2.1d Help, Index, Macro Translation Assistant,
Problematic Lotus 1-2-3 Macros, Problematic Lotus 1-2-3 Commands

Article ID: 77751 – Last Review: November 2, 2013 – Revision: 2.0


Applies to
  • Microsoft Excel 97 Standard Edition
  • Microsoft Excel 95 Standard Edition
kbnosurvey kbarchive KB77751

See the article here:
Lotus Macros That Do Not Directly Translate into Excel

PRB: #deleted seen when SQL Server 7.0 tables or SQL Server 6.5 tables that are linked to Access 97 or Access 2000 are opened

If Microsoft Access 97 or Microsoft Access 2000 is used to link SQL Server 6.5 or 7.0 tables that have numeric and text field columns, #deleted is seen in alternate rows if the SQL Server database is created by using non default code pages and Sort Order. This behavior can be reproduced when code pages are cp850 or cp437, and the sort order is binary, case insensitive.

This error is only seen with the Microsoft ODBC SQL Server Driver version 3.70.0623.

To work around this problem, clear the Perform translation for character data option when configuring the data source name (DSN).
This problem does not exist with previous or later versions of the Microsoft ODBC SQL Server Driver.
Additionally, using the Microsoft ODBC SQL Server Driver version 3.70.0623 with a pass-through query does not generate the #delete error.

Steps to reproduce the behavior

/* From the ODBC Administrator version 3.510.3711 (MDAC 2.1 SP1(GA)) */

  1. Create a system DSN that uses SQL Server 7.0, using the default settings, and connect to the pubs database.
  2. Using Microsoft Access, link the Employee and Discounts tables through the DSN created in step 1. Open the linked tables and you will see #deleted in alternate rows.
  3. Run a SQL specific pass-through query using the same DSN and then run either of the following SQL statements:
       Select * from employee
       Select * from discounts
    						

    The data returns correctly unlike the data in the linked tables.

  4. Close Microsoft Access 97 or 2000. Open the ODBC Administrator and re-configure the system DSN so that the Perform translation for character data option check box is clear (the check box is selected by default).
  5. Open Microsoft Access 97 or 2000 again, and then connect to these linked tables and the data returns correctly.
  6. Run a SQL specific pass-through query using the re-configured DSN, and then run either of the following SQL statements :
       Select * from employee
       Select * from discounts
    					

    Again, the data returns correctly.

Article ID: 236825 – Last Review: November 2, 2013 – Revision: 7.0


Applies to
  • Microsoft SQL Server 6.5 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Access 97 Standard Edition
kbnosurvey kbarchive kbdatabase kbmdacnosweep kbpending kbprb KB236825

View article:
PRB: #deleted seen when SQL Server 7.0 tables or SQL Server 6.5 tables that are linked to Access 97 or Access 2000 are opened

ACC2000: Choosing a New Printer Resets Printer Settings

When you choose a new printer in Microsoft Access 2000, some of the printer settings for your forms and reports are changed.
This functionality is controlled by the Microsoft Windows Common Dialog dynamic-link library (DLL). The same behavior occurs in Microsoft Write.
Microsoft Access retains certain printer settings with form and report
objects.

Some of these settings are not transferable between printer drivers. This being the case, when the printer driver is changed from within the
report, some settings revert to the default settings for that printer.

This behavior occurs when the printer is explicitly changed in the File Print Setup option in the report, or when the printer is implicitly changed in the report by changing the default printer in Windows.

This behavior can also occur when the printer port is changed.

Article ID: 209757 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbprb kbprint KB209757

Read the original:
ACC2000: Choosing a New Printer Resets Printer Settings

Page 323 of 951« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories