-
Notifications
You must be signed in to change notification settings - Fork 18
/
Copy pathREADMERP.HTM
1418 lines (1220 loc) · 63.3 KB
/
READMERP.HTM
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<html>
<!----------------------------------------------------------------------------->
<!-- BEGIN HTML HEAD -->
<head>
<title>Microsoft Repository Readme</title>
<meta name="MS-HAID" content="readmerp">
</head>
<body BGCOLOR="#FFFFFF" onclick="checkExpand()">
<font face="Verdana, Arial, Helvetica, sans-serif" size="2" color="#000000" link="#0000FF"
vlink="#660066"><!-- -->
<!-- END HEADER -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN JSCRIPT -->
<!-- -->
<script language="JSCRIPT">
function checkExpand( )
{
if ("" != event.srcElement.id)
{
var ch = event.srcElement.id + "Child";
var el = document.all[ch];
if (null != el)
{
el.style.display = "none" == el.style.display ? "" : "none";
if (el.style.display != "none")
event.returnValue=false;
}
}
}
</script>
<!-- -->
<!-- END JSCRIPT -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN README INTRO -->
<!-- -->
<h2>Microsoft Repository 2.0 Readme </h2>
<p>© 1998 Microsoft Corporation. All rights reserved. </p>
<p>Repository Readme includes updated information for the documentation provided with
Microsoft® Visual Studio -- Development System for Windows and the Internet. The
information in this document is more up-to-date than the information in the Help system.
Many of the issues outlined in this document will be corrected in upcoming releases.</p>
<p>For <i>general installation issues</i> on the Visual Studio 6.0 suite of products,
including side by side product installation, see the <a href="install.htm"
title="Jumps to the installation readme (install.htm).">Installation Notes</a> readme
(install.htm).</p>
<p>For other issues on the Help system of the Visual Studio suite of products, go to <font
face="Verdana, Arial, Helvetica, sans-serif" size="2" color="#000000" link="#0000FF"
vlink="#660066"><a href="readmeDN.htm" title="Jumps to readmeDN.htm">MSDN™, the
Microsoft Developer Network Readme.</a></p>
<!-- -->
<!-- END README INTRODUCTION -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN TOC -->
<!-- -->
<h3>Contents </h3>
<!------------------------------------------------------------------->
<!-- SECTION 1.0 -->
<!-- -->
<h5><a class="ex" href="#" title="Click to expand or collapse." id="Section1">Repository
Overview</a></h5>
<div id="Section1Child"><a href="#Topic_10">
<p>What is Microsoft Repository?</a> </p>
<p><font color="#FF0000" size="1" face="Verdana,Arial,Helvetica"><strong>NEW</strong></font>
<a href="#Topic_11">What is New in Microsoft Repository 2.0</a> </p>
<p><a href="#Topic_12">Important Information for Release 2.0 Customers</a></p>
</div><!------------------------------------------------------------------->
<!-- SECTION 2.0 -->
<!-- -->
<h5><a class="ex" href="#" title="Click to expand or collapse." id="Section2">Installation</a></h5>
<div id="Section2Child">
<p><b>Important:</b> This section contains vital information about
installing Repository 2.0. Please read all items carefully before you begin your
installation.</p>
<a href="#Topic_20">
<p>Repository Installation Notes</a></p>
<p><a href="#Topic_21">Repository Files on Your Hard Disk</a> </p>
</div><!------------------------------------------------------------------->
<!-- SECTION 3.0 -->
<!-- -->
<h5><a class="ex" href="#" title="Click to expand or collapse." id="Section3">Repository
2.0 Issues</a></h5>
<div id="Section3Child"><a href="#Topic_30">
<p>Differences between Repository 1.0 and Repository 2.0</a></p>
<a href="#Topic_31">
<p>Asynchronous Operation</a></p>
<a href="#Topic_32">
<p>SQL and API Types Used in Property Definitions</a></p>
<a href="#Topic_33">
<p>New Features</a></p>
</div><!------------------------------------------------------------------->
<!-- SECTION 4.0 -->
<!-- -->
<h5><a class="ex" href="#" title="Click to expand or collapse." id="Section4">Limitations
and More Information</a></h5>
<div id="Section4Child"><a href="#Topic_40">
<p>Known Limitations in Microsoft Repository 2.0</a></p>
<p><a href="#Topic_41">For More Information</a> </p>
</div><!-- -->
<!-- END CONTENTS TOC -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN CONTENTS -->
<!-- -->
<!-- -->
<!------------------------------------------------------------------->
<!-- SECTION 1.0 -->
<!-- -->
<p><br>
</p>
<h3>Repository Overview</h3>
<p><br>
<!------------------------------------------------------><!-- TOPIC 1.0 --><!-- --></p>
<h4><a name="Topic_10"></a>What Is Microsoft Repository?</h4>
<p>Microsoft Repository is an enabling technology for defining and populating information
models. It is used by engineering and software development tools to share information
about engineered artifacts. Engineered artifacts are things like software components,
manufactured components, documents, maps, Web pages - anything about which you might want
to share information that has complex structure. Microsoft Repository stores repository
data in a relational database. Two database management systems are supported: Microsoft<i>®</i>
SQL Server version 6.5 or later and the Microsoft Jet database engine version 3.0 or
later. </p>
<p><!------------------------------------------------------><!-- TOPIC 1.1 --><!-- --></p>
<h4><a name="Topic_11"></a></h4>
<h4>What Is New in Microsoft Repository 2.0?</h4>
<p>Microsoft Repository 2.0 contains significant enhancements in the areas of version
management and team development while maintaining backward compatibility with Microsoft
Repository 1.0 interfaces. </p>
<p>The major areas of new functionality are:
<ul>
<li><b>Versioning of objects</b>: allows the repository user to maintain multiple versions
of repository objects. </li>
<li><b>Versioning of relationships</b>: allows the repository user to maintain multiple
versions of relationships between objects. </li>
<li><b>Workspace management</b>: provides a virtual repository for users in which they can
manipulate private versions of objects and relationships. A Checkin/Checkout model allows
users to control what information is visible in the users' workspaces and what changes are
made visible to other users. This new functionality is described in detail in the user
documentation and specifications that accompany the software. </li>
</ul>
<p><br>
<!------------------------------------------------------><!-- TOPIC 1.2 --><!-- --></p>
<h4><a name="Topic_12"></a>Important Information for Release 2.0 Customers</h4>
<p>Users should also be aware of the following:
<ul>
<li>Microsoft Repository 2.0 is backward-compatible with version 1.0 functionality and
interfaces. If all of the applications using a repository database use only version 1.0
functionality, no incompatibilities will occur. Likewise, if all the applications using a
repository database are version- and workspace-aware, they should be successful. Mixing
applications that are version-aware with applications that are not version- and
workspace-aware on the same repository database is not recommended. </li>
<li>The Microsoft Repository 2.0 SQL schema is an extension of the Microsoft Repository 1.0
schema because of the introduction of versioning. Applications that bypass repository
interfaces to access SQL tables directly may have to modify queries or provide views for
backward compatibility. </li>
<li>The migration wizard (MigRepV2.exe) converts Microsoft Repository underlying database
information from version 1.0 to version 2.0 (SQL to SQL, and Jet to Jet). You must have
the Microsoft Repository engine version 2.0 (V2 engine) registered before running the
migration wizard. Notice that the migration is one way only, from version 1.0 to version
2.0. </li>
<li>Microsoft Repository 2.0 provides no support for the WRITETHROUGH mode of transaction
execution. </li>
<li>Microsoft Repository 2.0 supports Intel x86 and Alpha platforms. </li>
</ul>
<p> </p>
<p><br>
<!-------------------------------------------------------------------><!-- SECTION 2.0 --><!-- --></p>
<h3>Installation</h3>
<!------------------------------------------------------>
<!-- TOPIC 2.0 -->
<!-- -->
<h4><a name="Topic_20"></a>Repository Installation Notes</h4>
<p>Microsoft Repository is installed during a Visual Basic installation. </p>
<p>Microsoft Repository requires that the Data Access component be installed. By default,
the Data Access component is installed during a Visual Basic installation. However, if you
choose not to install the Data Access component, and then install a third party tool that
uses Microsoft Repository, you will encounter the following error when starting Visual
Basic 98:</p>
<p><em>"An error occurred while opening the Microsoft Repository database. Specified
driver could not be loaded due to system error 126 (Microsoft Access Driver (*.MDB)).
Microsoft Repository Add-in for Visual Basic is shutting down."</em></p>
<p>To correct this problem, install the Data Access component.</p>
<p><br>
<!------------------------------------------------------><!-- TOPIC 2.1 --><!-- --></p>
<h4><a name="Topic_21"></a>Repository Files on Your Hard Disk</h4>
<p>The following files will be added to the Windows SYSTEM (or SYSTEM32) directory:
<ul>
<li>REPUTIL.DLL - Utilities for the Repository engine </li>
</ul>
<p>The following files will be added to the "Program Files\Common Files\Microsoft
Shared\Repostry" directory:
<ul>
<li>REPODBC.DLL - The Repository Engine</li>
<li>REPRC.DLL - Resources for the Repository Engine</li>
<li>REPBROWS.EXE - A basic Repository Browser</li>
<li>REPBRRC.DLL - Resources for the Repository Browser</li>
<li>MIGREPV2.EXE - The Migration Wizard User Interface</li>
<li>MIGV2RC.DLL - Resources for the Migration Wizard</li>
<li>MIGV2.DLL - The Migration Wizard Algorithm</li>
<li>REPCDLG.DLL - The Repository Common Dialog</li>
<li>REPCDLG.OCX - ActiveX controls for the Repository Common Dialog</li>
<li>REPCDRC.DLL - Resources for the Repository Common Dialog</li>
</ul>
<p>The following files will be added to the "Program Files\Common Files\Microsoft
Shared\Repostry\infoMdl" directory:
<ul>
<li>REPCDE.DLL - The Component Description Information Model</li>
<li>REPCOM.DLL - The COM Information Model</li>
<li>REPDTM.DLL - The Data Type Information Model</li>
<li>REPGEN.DLL - The Generic Information Model</li>
<li>UML.DLL - The Unified Modeling Language (UML) Information Model</li>
<li>REPUMX.DLL - The UML Extension Information Model</li>
<li>REPVCM.DLL - The Visual Component Manager Model</li>
</ul>
<p>The following files will be added to the Visual Basic directory:
<ul>
<li>REPVB.DLL - The Repository Add-in for Visual Basic</li>
<li>REPVBRC.DLL - Resource file for Repository Add-in</li>
<li>REPVBTIM.DLL - Type definitions for the MDO Model</li>
</ul>
<p><!-- TOPIC 2.2 --><!-- --></p>
<h3><a name="Topic_22"></a><font face="Verdana" size="2"><br>
<!-------------------------------------------------------------------><!-- SECTION 3.0 --><!-- --></h3>
<h3>Repository 2.0 Issues</font></h3>
</font><font face="Verdana" size="2"><!------------------------------------------------------>
<!-- TOPIC 3.0 -->
<!-- -->
<h4><a name="Topic_30"></a>Differences Between Repository 1.0 and Repository 2.0</h4>
<b><font SIZE="4">
<h5></font></b>Repository 1.0 Usage</h5>
<p ALIGN="JUSTIFY">If the repository database was created using the Repository 1.0 engine
and has been used for information model creation, population, and retrieval only through
this engine, there will be some differences when you run the same application with the
Repository 2.0 engine. The differences arise from the treatment of relationships, as
listed below:</p>
<ul>
<li>In Repository 1.0, if an application inserts a name-unique relationship with an existing
name, the name-uniqueness violation is caught immediately. In Repository 2.0, the
violation is caught immediately only if the existing relationship is in the cache (for
example, created as part of the same transaction or retrieved into the cache already).
Otherwise, the name-uniqueness validation occurs at commit time.</li>
</ul>
<ul>
<li>Enumerators in the Repository 1.0 engine, except those for relationship collections,
have static contents, so added items do not appear until a new enumerator is requested
from the collection. In the Repository 2.0 engine, enumerators are dynamic, so added items
appear immediately in the enumerator.</li>
</ul>
<ul>
<li>In Repository 1.0, if the insertion position in <strong>IRelationshipCol::Insert()</strong>
is larger than the current count of the collection, the call is treated as <strong>IRelationshipCol::Add()</strong>.
In Repository 2.0, if the specified insertion position is one greater than the current
count, then the call reduces to <strong>IRelationshipCol::Add()</strong>. For higher
insertion positions, the call returns an error since the user presumably made a mistake
(it would be bad programming in any case).</li>
</ul>
<ul>
<li>Invoking <strong>IRelationshipCol::Insert()</strong> on a nonsequenced or destination
collection results in an error in Repository 2.0. In Repository 1.0, the call performs <strong>IRelationshipCol::Add()</strong>
on the origin if the collection is sequenced.</li>
</ul>
<b><u>
<p></u>Mixed-mode Repository 1.0 and Repository 2.0 Usage</b></p>
<p ALIGN="left">It is conceivable that a Repository 1.0 application might be run on the
Repository 2.0 engine, in which versioning operations are performed by other applications
on the same repository. The engine of course has to respect the semantics of versioning,
and some of those semantics will necessarily be visible to the nonversioning application.
A Repository 1.0 application can <em>only</em> see these effects when operating on a
repository database in which Repository 2.0 applications are performing version and
workspace operations. These effects do not arise when all applications on a repository
database are following Repository 1.0 semantics. In addition to the effects mentioned
above, the following could arise:</p>
<ul>
<li>A Repository 1.0 application can retrieve an object using <strong>get_Object()</strong>
(it gets the resolved version), delete it (the version is deleted), and still use <strong>get_Object()</strong>
a second time (the call resolves to a different version). </li>
</ul>
<ul>
<li>Since all objects are unfrozen in Repository 1.0, updates never failed in Repository
1.0. However, in Repository 2.0, all update operations (property and origin collection
updates) on a frozen version or a checked-out version will fail. </li>
</ul>
<ul>
<li>In Repository 2.0, a delete operation on a checked-out version or a version with a
successor will fail. Neither of these situations could arise in Repository 1.0.</li>
</ul>
<ul>
<li>In Repository 1.0, <strong>IRelationship::Delete()</strong> removes the relationship
entirely so that the relationship no longer exists at the origin or the destination
objects. In Repository 2.0, if we have navigated from the destination side, the
relationship from the origin version to any other versions of the destination continues to
exist after the deletion. If we have navigated from the origin side, the relationship from
that version to all versions of the destination in the relationship is removed. Similar
behavior holds true for <strong>IRelationshipCol::Remove()</strong> and <strong>ITargetObjectCol::Remove()</strong>.</li>
</ul>
<ul>
<li>In Repository 1.0, delete propagation stops at an object if it is the destination of
some other relationship of the same type. In Repository 2.0, in addition to this
condition, delete propagation stops at an unchangeable version (frozen or checked out to a
different workspace) and versions that have incoming relationships (of any type) from a
frozen origin (that is, no error).</li>
</ul>
<b><u>
<p></u>SQL Tables</b>
<ul>
<li><p ALIGN="left">The Repository 2.0 SQL tables are extensively revised for versioning.
SQL views that match Repository 1.0 SQL queries executed on a repository database in which
all objects have one version should work with no change. </p>
</li>
<li><p ALIGN="left">Repository 1.0 SQL queries executed on a repository in which multiple
versions of objects exist will likely execute to completion, but their semantics should be
reviewed in light of versioning. In certain situations multiple versions of the same
object may be returned by the queries, which a Repository 1.0 application might not
expect.</p>
</li>
<li><font size="2"><p align="left">The table <strong>RTblSites</strong> does not have the <strong>NextLocalID</strong>
column in Repository 2.0.</p>
</font></li>
<li><p align="left">The table <strong>RTblClassDefs</strong> has a new column called <strong>VerPropDescs</strong>
where the class definition is stored in Repository 2.0. The column <strong>PropDescs</strong>
contains only null values and is no longer used. However, it is retained for
compatibility.</p>
</li>
</ul>
<b><u>
<p></u>Miscellaneous</b> </p>
<p ALIGN="JUSTIFY">The following table shows other differences between Repository 1.0 and
Repository 2.0.</p>
</font>
<table BORDER="1" CELLSPACING="1" BORDERCOLOR="#000000" CELLPADDING="7" WIDTH="600">
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1"><b>Description</b></font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1"><b>V1 engine</b></font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1"><b>V2 engine</b></font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font color="#000000" face="Verdana" size="1">IRepositoryItem::get_Item()</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Out of range integer index
returns EREP_BADPARAMS.</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Out of range integer index
returns DISP_E_BADINDEX.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">IRelationshipCol::Insert()</font><p><font
face="Verdana" size="1">ITargetObjectCol::Insert()</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Insert appends to the
collection if the collection is a nonsequenced. </font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Insert fails for nonsequenced
collections (EREP_COL_NOT-SEQUENCED) and destination collections (EREP_RELSHIP_ORGONLY).</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">IRelationshipCol::Move()</font><p><font
face="Verdana" size="1">ITargetObjectCol::Move()</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Fails with EREP_RELSHIP_
ORGONLY for nonsequenced and destination collections.</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Fails with
EREP_COL_NOT-SEQUENCED for nonsequenced collections, and EREP_RELSHIP_ ORGONLY for
destination collections.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">IRepositoryObjectVersion::put_Name()</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Error
EREP_OBJ_NO-NAMING-RELSHIP is not added to the error queue.</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Error REP_OBJ_NONAMING-RELSHIP
is added to the error queue.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">Unique naming collections: Item
B with name "B" is added multiple times to a unique naming collection </font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Error code is
EREP_RELSHIP_DUPENAME.</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Error code is
EREP_RELSHIP_EXISTS.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">IRepositoryItem::get_Name()</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Succeeds on a non-naming
relationship (returns "0").</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Fails.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">IRelationshipCol::get_Item() </font><p><font
face="Verdana" size="1">ITargetObjectCol:: get_Item()</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Argument can be INTID, OBJID,
Index, or Name.</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Argument can be OBJID, Index,
or Name.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">ExecuteQuery() on SQL Server</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Checks for INTID column in
result set. </font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Accepts more than just INTID
whenever implicit conversion is possible.</font></td>
</tr>
<tr>
<td WIDTH="343" VALIGN="TOP"><font face="Verdana" size="1">Refresh on object instances
collection</font></td>
<td WIDTH="300" VALIGN="TOP"><font face="Verdana" size="1">Refreshes properties and then
objects.</font></td>
<td WIDTH="272" VALIGN="TOP"><font face="Verdana" size="1">Refreshes objects and then
properties.</font></td>
</tr>
</table>
<font face="Verdana" size="2">
<p> </p>
<!------------------------------------------------------>
<!-- TOPIC 3.1 -->
<!-- -->
<h4><a name="Topic_31"></a>Asynchronous Operation</h4>
<p ALIGN="left">Loading of object collections in response to <strong>IRepositoryODBC::ExecuteQuery()</strong>
can be asynchronous. The calling thread should check to determine whether the load is
complete. If the calling thread tries to read data, refresh the collection, or construct
an enumerator while loading is in progress, it will be blocked until the load is complete.</p>
<b><u>
<h5></u>Flags </h5>
<ul>
</b>
<li>For setting/clearing "async" option:</li>
</ul>
<dir>
<dir>
<dl>
<dt></font><font face="Courier New" size="2">RODBC_RESET_OPTIONS = 1 // Reset all
options</font></dt>
<dt><font face="Courier New" size="2">RODBC_ASYNCH = 2
// Asynchronous query execution</font><font
face="Verdana" size="2"></dt>
</dl>
<u><b>
</dir>
</dir>
<ul>
</b></u>
<li>For loading status of object:</li>
</ul>
<blockquote>
<dl>
<dd><font face="Courier New" size="2">READY = 1
//
Loading is complete</font></dd>
<dd><font face="Courier New" size="2">INPROGRESS = 2
// Loading in progress</font></dd>
<dd><font face="Courier New" size="2">CANCELLED = 3
// Loading has been
cancelled (by caller)</font></dd>
<dd><font face="Courier New" size="2">FAILED = 4
//
Loading failed (reason unknown)</font></dd>
</dl>
</blockquote>
<b><u>
<h5></u>New Interfaces </h5>
<ul>
</b>
<li><strong>IObjectCol2</strong> -- inherits from <strong>IObjectCol</strong>. </li>
</ul>
<blockquote>
<p>Additional methods:</p>
</blockquote>
<blockquote>
<ul>
<li><strong>LoadStatus</strong>: Obtains the load status of the collection.</li>
</ul>
</blockquote>
<blockquote>
<blockquote>
<h6>Signature</h6>
</blockquote>
<blockquote>
<dl>
<dt><strong>HRESULT LoadStatus(long</strong> *<em>piStatus</em><strong>)</strong>
// Automation</dt>
<dt><strong>HRESULT get_LoadStatus(long</strong> *<em>piStatus</em><strong>) </strong>
// COM</dt>
</dl>
<h6>Arguments</h6>
</blockquote>
</blockquote>
<ul>
<dl>
<dd><em>piStatus</em> </dd>
<dd>[out, retval] </dd>
<dd>One of READY/INPROGRESS/CANCELLED/FAILED.</dd>
</dl>
</ul>
<blockquote>
<blockquote>
<h6>Return value</h6>
</blockquote>
</blockquote>
<ul>
<dl>
<dd>S_OK if successful, EREP_BADPARAMS if no output argument is provided.</dd>
</dl>
</ul>
<blockquote>
<ul>
<li><strong>Cancel</strong>: Requests the cancellation of the ongoing load operation.</li>
</ul>
</blockquote>
<blockquote>
<blockquote>
<h6>Signature</h6>
</blockquote>
<blockquote>
<p><strong>HRESULT</strong> <strong>Cancel()</strong></p>
</blockquote>
</blockquote>
<blockquote>
<blockquote>
<h6>Return value</h6>
</blockquote>
</blockquote>
<blockquote>
<dl>
<dd>S_OK.</dd>
</dl>
</blockquote>
<ul>
<li><strong>IRepositoryODBC2</strong> -- inherits from <strong>IRepositoryODBC</strong>. </li>
</ul>
<blockquote>
<p>Additional methods:<ul>
<li><strong>GetOption: </strong>Obtains the value of the load option.</li>
</ul>
</blockquote>
<blockquote>
<blockquote>
<h6>Signature</h6>
<p><strong>HRESULT</strong> <strong>GetOption(long</strong> <em>iOption</em>, <strong>VARIANT</strong>
*<em>psValue</em><strong>)</strong></p>
</blockquote>
<dl>
<dd><h6>Arguments</font></h6>
<font face="Verdana" size="2"></dd>
<dd><em>iOption</em> </dd>
<dd>[in] </dd>
<dd>RODBC_ASYNCH.</dd>
<dd> </dd>
<dd><em>psValue</em> </dd>
<dd>[out, retval] </dd>
<dd>VARIANT_TRUE or VARIANT_FALSE, depending upon whether the RODBC_ASYNCH option has been
set.</dd>
<dd> </dd>
<dd><h6>Return value</font></h6>
<font face="Verdana" size="2"></dd>
<dd>S_OK if successful, EREP_BADPARAMS if any other option is specified.</dd>
</dl>
</blockquote>
<blockquote>
<dir>
<li><strong>SetOption: </strong>Sets the option for loading the collection. The async flag
can be set if and only if the underlying database system supports the async operation.</li>
</dir>
</blockquote>
<blockquote>
<blockquote>
<dl>
<h6>Signature</h6>
<dt><strong>HRESULT</strong> <strong>SetOption(long</strong> <em>iOption</em>, <strong>VARIANT</strong>
<em>sValue</em><strong>)</strong></dt>
</dl>
<h6>Input Arguments</h6>
<dl>
<dt><em>iOption</em> RODBC_ASYNCH and <em>sValue</em> TRUE sets the async mode of load.</dt>
<dt><em>iOption</em> RODBC_ASYNCH and <em>sValue</em> FALSE clears the async mode.</dt>
<dt><em>iOption</em> RODBC_RESET_OPTIONS resets the async mode of load.</dt>
</dl>
</blockquote>
</blockquote>
<blockquote>
<blockquote>
<h6>Return value</h6>
<p>S_OK if successful, EREP_TYPE_COLMISMATCH if a value other than TRUE or FALSE is
specified in sValue when iOption is RODBC_ASYNCH.</p>
</blockquote>
</blockquote>
<b><u>
<p></u>Other Changes
<ul>
</b>
<li>Class <strong>ObjectCol</strong> supports both <strong>IObjectCol</strong> [default] and
<strong>IObjectCol2</strong>.</li>
</ul>
<ul>
<li><strong>IObjectCol2::Refresh()</strong> asynchronously refreshes the object collection
(reloads object collection and refreshes target objects) when the async mode is in effect.
The calling thread should check to determine whether refresh is complete. If the calling
thread tries to read data, refresh the collection, or construct an enumerator while
refresh is in progress, it will be blocked until refresh is complete.</li>
</ul>
<!------------------------------------------------------>
<!-- TOPIC 3.2 -->
<!-- -->
<p> </p>
<h4><a name="Topic_32"></a>SQL and API Types Used in Property Definitions</h4>
<!------------------------------------------------------>
<!-- TOPIC 3.3 -->
<!-- -->
<p>The following two tables show the API types recognized by the Repository engine, as
well as the SQL types. These values appear in the <b>APIType</b> and <b>SQLType</b>
properties of a <b>PropertyDef</b> Object. For information on conversion between SQL and
API types, please refer to the ODBC Programmer's Reference.</p>
</font>
<table BORDER="1" CELLSPACING="1" BORDERCOLOR="#000000" CELLPADDING="9" WIDTH="331">
<tr>
<td VALIGN="TOP" COLSPAN="2"><font face="Verdana" size="1"><b>API TYPES RECOGNIZED BY
ENGINE</b></font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1"><b>API TYPE</b></font></td>
<td WIDTH="36%" VALIGN="TOP"><b><p ALIGN="CENTER"><font face="Verdana" size="1">VALUE</font></b></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_UTINYINT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-28</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_STINYINT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-26</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_ULONG</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-18</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_USHORT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-17</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_SLONG</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-16</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_SSHORT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-15</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_BINARY</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-2</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_TINYINT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-6</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_BIT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-7</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_CHAR</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">1</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_LONG</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">4</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_SHORT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">5</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_FLOAT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">7</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_DOUBLE</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">8</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_DATE</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">9</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_TIME</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">10</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_C_TIMESTAMP</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">11</font></td>
</tr>
</table>
<font face="Verdana" size="2"><font SIZE="2">
<p></font> </p>
</font>
<table BORDER="1" CELLSPACING="1" BORDERCOLOR="#000000" CELLPADDING="9" WIDTH="331">
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1"><b>SQL TYPE</b></font></td>
<td WIDTH="36%" VALIGN="TOP"><b><p ALIGN="CENTER"><font face="Verdana" size="1">VALUE</font></b></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_LONGVARCHAR</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-1</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_BINARY</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-2</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_VARBINARY</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-3</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_LONGVARBINARY</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-4</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_BIGINT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-5</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_TINYINT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-6</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_BIT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">-7</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_CHAR</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">1</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_NUMERIC</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">2</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_DECIMAL</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">3</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_INTEGER</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">4</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_SMALLINT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">5</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_FLOAT</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">6</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_REAL</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">7</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_DOUBLE</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">8</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_DATETIME</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">9</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_TIME</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">10</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_TIMESTAMP</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">11</font></td>
</tr>
<tr>
<td WIDTH="64%" VALIGN="TOP"><font face="Verdana" size="1">SQL_VARCHAR</font></td>
<td WIDTH="36%" VALIGN="TOP"><p ALIGN="CENTER"><font face="Verdana" size="1">12</font></td>
</tr>
</table>
<font face="Verdana" size="2">
<p> </p>
<h4><a name="Topic_33"></a>New Features</h4>
<h5>Properties</h5>
<p>Two new properties have been added to the <strong>IRepository2</strong> interface to
indicate the version of the database file.
<ul>
<li><strong>MajorDBVersion</strong></li>
</ul>
<blockquote>
<h6>Signature</h6>
<dl>
<dt><strong>HRESULT MajorDBVersion(long</strong> *<em>piMajorDBVersion</em><strong>)</strong>
// Automation</dt>
<dt><strong>HRESULT get_MajorDBVersion(</strong> long *<em>piMajorDBVersion</em><strong>)</strong>
// COM</dt>
</dl>
<h6><i>Arguments</h6>
</i><dl>
<dt><em>piMajorDBVersion </em></dt>
<dt>[out, retval] </dt>
<dt>The major version number of the first Repository engine version that introduced this
database format.</dt>
</dl>
</blockquote>
<ul>
<li><strong>MinorDBVersion</strong></li>
</ul>
<blockquote>
<h6>Signature</h6>
<dl>
<dt><strong>HRESULT MinorDBVersion(long</strong> *<em>piMinorDBVersion</em><strong>)</strong>
// Automation</dt>
<dt><strong>HRESULT get_MinorDBVersion(</strong> long *<em>piMinorDBVersion</em><strong>)</strong>
// COM</dt>
</dl>
<h6><i>Arguments</h6>
</i><dl>
<dt><em>piMinorDBVersion </em></dt>
<dt>[out, retval] </dt>
<dt>The minor version number of the first Repository engine version that introduced this
database format.</dt>
</dl>
</blockquote>
<!------------------------------------------------------>
<!-- TOPIC 4.0 -->
<!-- -->
<h5>Methods</h5>
<p>A new method <strong>CreateObjectEx()</strong> has been added to the interface <strong>IRepository2</strong>.<strong>
</strong>It creates the first version of a new Repository object of the specified type.
The newly created version is assigned the object-version identifier passed in as an
argument, unlike <strong>IRepository::CreateObject()</strong>, in which the Repository
assigns the version ID. It has the following syntax:</p>
<blockquote>
<i><b><h6></b></i>Signature<i><b></h6>
</b></i><dl>
<dt><strong>HRESULT IRepository2::CreateObjectEx(</strong></dt>
<dt><strong>VARIANT</strong> <em>TypeID,</em></dt>
<dt><strong>VARIANT</strong> <em>ObjectID,</em></dt>
<dt><strong>VARIANT</strong> <em>ExtVersionID,</em></dt>
<dt><strong>IRepositoryObjectVersion</strong> <em>**ppRepObjVer</em><strong>)</strong>;</dt>
</dl>
<b><i><h6></i></b>Arguments</h6>
<dl>
<dt><em>TypeID</em> </dt>
<dt>[in] </dt>
<dt>It does the same work as<strong> IRepository::CreateObject</strong></dt>
<dt> </dt>
<dt><em>ObjectID</em> </dt>
<dt>[in] </dt>
<dt>It does the same work as <strong>IRepository::CreateObject</strong> </dt>
<dt> </dt>
<dt><em>ExtVersionID</em> </dt>
<dt>[in] </dt>
<dt>This is the object-version identifier (20 bytes) to be assigned to the first version of
the object</dt>
<dt> </dt>
<dt><em>ppRepObjVer</em> </dt>
<dt>[out] </dt>
<dt>This is the <strong>IRepositoryObjectVersion</strong> pointer to the newly created
version</dt>
</dl>
</blockquote>
<p> </p>
<h3><a name="Topic_40"></a>Known Limitations in Microsoft Repository 2.0</h3>
<b>
<h4>1. Limitations related to interfaces and associated methods</b></h4>
<p><b>IRepositoryObjectVersion</b>
<ul>
<li><b>MergeVersion()</b>: Relationships are inserted at the end of the sequenced
collection. </li>