|
2635
- Microsoft Access is unable to change the password because the
old password doesn't match the password of the currently logged
in user.
2636 - Workgroup file
already exists.
2637 - Unable to start SQL
Server service. To restart the SQL Server service, double click
on the SQL Server System Manager icon in the system tray and
click Start/Continue. Once the service is started, point to
Connection on the File menu in Access and click OK.
2638 - Unable to start SQL
Server service. To restart the SQL Server service, double click
on the SQL Server System Manager icon in the system tray and
click Start/Continue. If the service fails to start, go to the
Services console and verify that the MSSQLServer service Log On
information is correct. Once the service is started, point to
Connection on the File menu in Access and click OK.
2646 - Microsoft Access
can't create this relationship and enforce referential integrity.
Data in the table ... violates referential integrity rules.For
example, there may be records relating to an employee in the
related table, but no record for the employee in the primary
table. Edit the data so that records in the primary table exist
for all related records.If you want to create the relationship
without following the rules of referential integrity, clear the
Enforce Referential Integrity check box.
2648 - Microsoft Access
created a one-to-one relationship instead of a one-to-many
relationship because there is a unique index on the field(s)
specified for the related table.If you want to define a
one-to-many relationship between these tables, try one of the
following:* Delete the one-to-one relationship, and then change
the setting of the Indexed property for the foreign key field
from No Duplicates to Duplicates OK.* Choose different matching
fields.
2649 - Microsoft Access
can't enforce referential integrity for this relationship. Make
sure the fields you drag are primary key fields or uniquely
indexed and that the unique index or primary key is correctly
set.If you want to create the relationship without following the
rules of referential integrity, clear the Enforce Referential
Integrity check box.
2650 - Microsoft Access
can't create this relationship and enforce referential integrity.
The fields you chose may have different data types.* The fields
may have the Number data type but not the same FieldSize
property setting. Try one of the following:* Select fields with
the same data type.* Open the tables in Design view, and change
the data types and field sizes so that the fields match.If you
want to create the relationship without following the rules of
referential integrity, clear the Enforce Referential Integrity
check box.
2651 - You can't create a
relationship between fields with the Memo, OLE Object, Yes/No,
or Hyperlink data type.You tried to enforce referential
integrity for a relationship, but one or more of the fields you
chose have the Memo, OLE Object, Yes/No, or Hyperlink data type.
Select fields in the grid that don't have these data types, or
open the tables in Design view and change data types.
2652 - You can't delete a
relationship inherited from a linked database.
2680 - The form or report
includes more OLE objects than Microsoft Access can display at
one time. Delete some of the bound or unbound object frames.
2683 - There is no object in
this control.
2684 - The OLE object is
empty.You can't edit a bound object frame if the field in the
underlying table doesn't contain an OLE object. Embed or link an
OLE object into the bound object frame using the Object command
on the Insert menu.
2685 - The object doesn't
have an OLE object data type. The bound object frame containing
the object you tried to edit isn't bound to a field with the OLE
object data type.If you want to display an OLE object, set the
ControlSource property for the bound object frame to a field
with the OLE object data type. Or use a different control, such
as a text box, to display the data.
2686 - Microsoft Access is
unable to save the ... object.Your computer ran out of disk
space while Microsoft Access was saving the OLE object.For
information on freeing disk space, search the Microsoft Windows
Help index for 'disk space, freeing'.
2687 - There was a problem
reading the ... object.
2690 - A system resource
necessary for displaying the ... object isn't available.Your
computer may be low on memory. Close unneeded programs, and try
the operation again.For more information on freeing memory,
search the Microsoft Windows Help index for 'memory,
troubleshooting'.
2691 - Microsoft Access
can't communicate with the OLE server. The OLE server may not be
registered. To register the OLE server, reinstall it.
2694 - The Clipboard isn't
available. The Clipboard may be in use by another application,
or your computer may be low on memory.If your computer is low on
memory, close unneeded programs, and then try the operation
again.For more information on freeing memory, search the
Microsoft Windows Help index for 'memory, troubleshooting'.
2695 - Microsoft Access is
unable to display the converted | object. Delete the object in
the bound object frame, and then re-create it.
2696 - Microsoft Access
can't read the OLE object. Delete the object in the bound object
frame, and then re-create it.
2697 - There was a problem
loading the ... object. The object you tried to create or edit
is not a valid OLE object. Re-create the object, and then embed
or link it again.
2698 - The ... object you
tried to create or edit is too large to save. Your database may
not contain enough space for the object.* Your computer may be
out of disk space.For information on freeing disk space, search
the Microsoft Windows Help index for 'disk space, freeing'.
2699 - The connection with
the OLE server was lost, or the OLE server encountered an error
while you were using it. Restart the OLE server, and then try
the operation again.
2700 - Microsoft Access
can't find an OLE server or a dynamic-link library (DLL)
required for the OLE operation. The OLE server or DLL may not be
registered. To register the OLE server or DLL, reinstall it.
< Previous
Next > |
|
|
