Sentence view
Universal Dependencies - English - LinES
| Language | English |
|---|
| Project | LinES |
|---|
| Corpus Part | train |
|---|
| Annotation | Ahrenberg, Lars |
|---|
showing 301 - 400 of 357 • previous
This could break your application and require rewriting your application.
s-301
en_lines-ud-train-doc1-301
This could break your application and require rewriting your application.
In Access 2000, you can only programmatically change the ANSI SQL query mode and any queries created under ANSI-92 mode were hidden in the Database window.
s-302
en_lines-ud-train-doc1-302
In Access 2000, you can only programmatically change the ANSI SQL query mode and any queries created under ANSI-92 mode were hidden in the Database window.
In Access 2002, you or a user can change ANSI SQL query mode through the user interface and ANSI-92 queries are no longer hidden in the Database window, so you should prevent accidental or intentional changes to the ANSI SQL query mode of your application by protecting your code and preventing the changing of the query mode through the application's user interface.
s-303
en_lines-ud-train-doc1-303
In Access 2002, you or a user can change ANSI SQL query mode through the user interface and ANSI-92 queries are no longer hidden in the Database window, so you should prevent accidental or intentional changes to the ANSI SQL query mode of your application by protecting your code and preventing the changing of the query mode through the application's user interface.
Using ambiguous aliases and column names.
s-304
en_lines-ud-train-doc1-304
Using ambiguous aliases and column names.
To avoid confusion, ensure that aliases and column names are always unique in an SQL statement.
s-305
en_lines-ud-train-doc1-305
To avoid confusion, ensure that aliases and column names are always unique in an SQL statement.
About how Access searches for reference libraries
s-306
en_lines-ud-train-doc1-306
About how Access searches for reference libraries
The Visual Basic project of a Microsoft Access file contains references to object libraries, and it can also contain references to other files, including other Access files.
s-307
en_lines-ud-train-doc1-307
The Visual Basic project of a Microsoft Access file contains references to object libraries, and it can also contain references to other files, including other Access files.
The locations of referenced files are specified in the References dialog box that is available from the References command on the Tools menu in the Visual Basic Editor.
s-308
en_lines-ud-train-doc1-308
The locations of referenced files are specified in the References dialog box that is available from the References command on the Tools menu in the Visual Basic Editor.
When you open an Access file, if Access doesn't find a referenced file in the specified location, it searches for the reference as follows.
s-309
en_lines-ud-train-doc1-309
When you open an Access file, if Access doesn't find a referenced file in the specified location, it searches for the reference as follows.
First, Access searches for a RefLibPaths key in the following location in the Microsoft Windows Registry:
s-310
en_lines-ud-train-doc1-310
First, Access searches for a RefLibPaths key in the following location in the Microsoft Windows Registry:
If the key exists, Access checks for the existence of a value name that matches the name of the referenced file.
s-311
en_lines-ud-train-doc1-311
If the key exists, Access checks for the existence of a value name that matches the name of the referenced file.
If it finds a matching value name, Access loads the reference from the path specified in the corresponding value data.
s-312
en_lines-ud-train-doc1-312
If it finds a matching value name, Access loads the reference from the path specified in the corresponding value data.
If Access doesn't find a RefLibPaths key, it searches for the referenced file in the locations listed below in the following order:
s-313
en_lines-ud-train-doc1-313
If Access doesn't find a RefLibPaths key, it searches for the referenced file in the locations listed below in the following order:
Application folder containing the application (the folder where Msaccess.exe is located).
s-314
en_lines-ud-train-doc1-314
Application folder containing the application (the folder where Msaccess.exe is located).
Current folder.
s-315
en_lines-ud-train-doc1-315
Current folder.
System folders (the System and System32 folders located in the Windows or WINNT folder).
s-316
en_lines-ud-train-doc1-316
System folders (the System and System32 folders located in the Windows or WINNT folder).
PATH environment variable.
s-317
en_lines-ud-train-doc1-317
PATH environment variable.
For more information about environment variables, see Windows Help.
s-318
en_lines-ud-train-doc1-318
For more information about environment variables, see Windows Help.
The folder that contains the Access file, and any subfolders located in that folder.
s-319
en_lines-ud-train-doc1-319
The folder that contains the Access file, and any subfolders located in that folder.
If Access still can't find the reference after performing this search, you must fix the reference manually.
s-320
en_lines-ud-train-doc1-320
If Access still can't find the reference after performing this search, you must fix the reference manually.
About saving an object as a data access page
s-321
en_lines-ud-train-doc1-321
About saving an object as a data access page
You can also save tables, views, stored procedures, functions, and forms in a Microsoft Access project as a data access page.
s-322
en_lines-ud-train-doc1-322
You can also save tables, views, stored procedures, functions, and forms in a Microsoft Access project as a data access page.
Saving an object as a data access page enables you to quickly convert an object into a page, and allows users of your application to review, enter, and analyze data over the Internet or an intranet.
s-323
en_lines-ud-train-doc1-323
Saving an object as a data access page enables you to quickly convert an object into a page, and allows users of your application to review, enter, and analyze data over the Internet or an intranet.
For example, if you have a sales report that you want to make available over the Web, instead of creating a data access page and customizing it to look like the sales report, you can save the report as a data access page.
s-324
en_lines-ud-train-doc1-324
For example, if you have a sales report that you want to make available over the Web, instead of creating a data access page and customizing it to look like the sales report, you can save the report as a data access page.
Using the Save As command on the File menu will save a data access page that is similar in appearance and functionality to the original report.
s-325
en_lines-ud-train-doc1-325
Using the Save As command on the File menu will save a data access page that is similar in appearance and functionality to the original report.
If you want to make changes to the design of the resulting page, you can open the page in Design view and make any changes you want.
s-326
en_lines-ud-train-doc1-326
If you want to make changes to the design of the resulting page, you can open the page in Design view and make any changes you want.
The default view – the view in which the object is open when you carry out the Save As command – determines the design of the data access page.
s-327
en_lines-ud-train-doc1-327
The default view – the view in which the object is open when you carry out the Save As command – determines the design of the data access page.
The following table lists the outcome of each view.
s-328
en_lines-ud-train-doc1-328
The following table lists the outcome of each view.
Default view (current view)
s-329
en_lines-ud-train-doc1-329
Default view (current view)
[30]
Outcome
s-330
en_lines-ud-train-doc1-330
Outcome
Datasheet view
s-331
en_lines-ud-train-doc1-331
Datasheet view
A page that has controls arranged as a datasheet
s-332
en_lines-ud-train-doc1-332
A page that has controls arranged as a datasheet
Form view
s-333
en_lines-ud-train-doc1-333
Form view
PivotTable view
s-334
en_lines-ud-train-doc1-334
PivotTable view
A page that uses a Microsoft Office PivotTable Component
s-335
en_lines-ud-train-doc1-335
A page that uses a Microsoft Office PivotTable Component
PivotChart view
s-336
en_lines-ud-train-doc1-336
PivotChart view
A page that uses a Microsoft Office Chart Component
s-337
en_lines-ud-train-doc1-337
A page that uses a Microsoft Office Chart Component
If you carry out the Save As command after making changes to the object's formatting, but before saving your changes, the current formatting – not the saved formatting – will be used to create the page.
s-338
en_lines-ud-train-doc1-338
If you carry out the Save As command after making changes to the object's formatting, but before saving your changes, the current formatting – not the saved formatting – will be used to create the page.
Implications of using the Save As command
s-339
en_lines-ud-train-doc1-339
Implications of using the Save As command
Control support
s-340
en_lines-ud-train-doc1-340
Control support
Such controls will be left unbound on a page.
s-341
en_lines-ud-train-doc1-341
Such controls will be left unbound on a page.
Subforms and subreports
s-342
en_lines-ud-train-doc1-342
Subforms and subreports
Subforms and subreports on a form or report are not converted when you carry out the Save As command.
s-343
en_lines-ud-train-doc1-343
Subforms and subreports on a form or report are not converted when you carry out the Save As command.
However, you can open the page in Design view and create additional group levels to make the page appear similar to the original object.
s-344
en_lines-ud-train-doc1-344
However, you can open the page in Design view and create additional group levels to make the page appear similar to the original object.
Control naming
s-345
en_lines-ud-train-doc1-345
Control naming
Controls on forms and reports need not have unique names, but names of controls on a page must be unique.
s-346
en_lines-ud-train-doc1-346
Controls on forms and reports need not have unique names, but names of controls on a page must be unique.
While creating the page, Access will change control names that are not unique.
s-347
en_lines-ud-train-doc1-347
While creating the page, Access will change control names that are not unique.
Controls in the header and footer sections
s-348
en_lines-ud-train-doc1-348
Controls in the header and footer sections
Controls in the Form, Report, or page header sections will be placed as unbound controls in the caption section of the outermost group level.
s-349
en_lines-ud-train-doc1-349
Controls in the Form, Report, or page header sections will be placed as unbound controls in the caption section of the outermost group level.
Controls in the Form, Report, or page footer sections will be placed as unbound controls in the navigation section of the outermost group level.
s-350
en_lines-ud-train-doc1-350
Controls in the Form, Report, or page footer sections will be placed as unbound controls in the navigation section of the outermost group level.
Code in a form or report that can not run from a data access page is imported into the page as a comment block at the end of the document.
s-351
en_lines-ud-train-doc1-351
Code in a form or report that can not run from a data access page is imported into the page as a comment block at the end of the document.
Pictures in a form or report are converted to bitmaps and placed in a folder named 'Images '.
s-352
en_lines-ud-train-doc1-352
Pictures in a form or report are converted to bitmaps and placed in a folder named 'Images '.
Group level properties
s-353
en_lines-ud-train-doc1-353
Group level properties
By default, the AllowAdditions, AllowDeletions, and AllowEdits properties of all group levels in a data access page created from a report are set to False.
s-354
en_lines-ud-train-doc1-354
By default, the AllowAdditions, AllowDeletions, and AllowEdits properties of all group levels in a data access page created from a report are set to False.
However, you can open the page in Design view and change the property settings.
s-355
en_lines-ud-train-doc1-355
However, you can open the page in Design view and change the property settings.
Expressions that refer to form or subform properties are ignored.
s-356
en_lines-ud-train-doc1-356
Expressions that refer to form or subform properties are ignored.
About sorting data in PivotTable or PivotChart view
s-357
en_lines-ud-train-doc1-357
About sorting data in PivotTable or PivotChart view
Edit as list • Text view • Dependency trees