انا عندي برنامج وزرد مكروسفر 97 وعملت قاعدة بينات ولكن ماعرفت كيف اعمل البرنامج الوزرة الرجو شرح ذلك ليي وبالغة العربية
ارجو كيف اعمل ستب على برنامج وزرد
مغلق
هل أنت متأكد من اسم البرنامج ؟
ما هي الوزرة ؟
هل الموضوع له علاقة بالاكسس ؟ أم من الافضل طرح السؤال فى قسم الدعم الفني؟
اخي هذ كلشي عن البرنامج وارجو ان يكون الد بالعربي END-USER LICENSE AGREEMENT FOR MICROSOFT SOFTWARE
IMPORTANT—READ CAREFULLY: This Microsoft End-User License Agreement (“EULA”) is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation for the Microsoft software product identified above, which includes computer software and may include associated media, printed materials, and “online” or electronic documentation (“SOFTWARE PRODUCT”). By installing, copying, or otherwise using the SOFTWARE PRODUCT, you agree to be bound by the terms of this EULA. If you do not agree to the terms of this EULA, do not install or use the SOFTWARE PRODUCT; you may, however, return it to your place of purchase for a full refund.
SOFTWARE PRODUCT LICENSE
The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold.
1. GRANT OF LICENSE. This EULA grants you the following rights:
a. Software Product.
أ. You may install and use one copy of the SOFTWARE PRODUCT, or any prior version for the same operating system, on a single computer. The primary user of the computer on which the SOFTWARE PRODUCT is installed may make a second copy for his or her exclusive use on a portable computer.
ب. Electronic Documents. Solely with respect to electronic documents included with the SOFTWARE, you may make an unlimited number of copies (either in hardcopy or electronic form), provided that such copies shall be used only for internal purposes and are not republished or distributed to any third party.
ج. Storage/Network Use. You may also store or install a copy of the SOFTWARE PRODUCT on a storage device, such as a network server, used only to install or run the SOFTWARE PRODUCT on your other computers over an internal network; however, you must acquire and dedicate a license for each separate computer on which the SOFTWARE PRODUCT is installed or run from the storage device. A license for the SOFTWARE PRODUCT may not be shared or used concurrently on different computers.
د. License Pak. If you have acquired this EULA in a Microsoft License Pak, you may make the number of additional copies of the computer software portion of the SOFTWARE PRODUCT authorized on the printed copy of this EULA, and you may use each copy in the manner specified above. You are also entitled to make a corresponding number of secondary copies for portable computer use as specified above.
ii. Redistributable Components. (Note: the Sample Code, Run-Time Files, and Replication Manager Files, each as defined below, are collectively referred to as “REDISTRIBUTABLES.”)
أ. Sample Code. In addition to the rights granted in Section 1(a), Microsoft grants you a nonexclusive, royalty-free right to use and modify those portions of the SOFTWARE PRODUCT identified as sample code (“Sample Code”) and to reproduce and distribute the object code form of the Sample Code, provided you comply with Section (B)(v), below.
ب. Redistributable Run-Time Components. In addition to the rights granted in Section 1(a), Microsoft grants you a nonexclusive royalty-free right to reproduce and distribute the object code version of those portions of the SOFTWARE listed in the SOFTWARE in the ODEEULA.TXT file (“Run-Time Files”), provided you comply with Section (B)(iv), below. In the event that you have obtained the SOFTWARE as an upgrade, subject to Section 3, the rights granted in this subsection also apply to the Run-Time Files identified in and provided with any prior version of the SOFTWARE.
ج. Additional Redistributable Components. In addition to the rights granted in Section 1(a), Microsoft grants you a nonexclusive, royalty-free right to reproduce and distribute the object code version of the SOFTWARE identified in the ODEEULA.TXT file as “Replication Manager Redistributable File Listing” (“Replication Manager Files”), provided you comply with Section (B)(v), below. In the event that you have obtained the SOFTWARE as an upgrade, subject to Section 3, the rights granted in this subsection also apply to the Replication Manager Files identified in and provided with any prior version of the SOFTWARE.
د. Redistribution Requirements—Run-Time Files. If you redistribute the Run-Time Files, you agree: (a) to distribute the Run-Time Files in object code only in conjunction with and as a part of a software product developed by you which adds significant and primary functionality to the SOFTWARE and which is developed to operate in the Windows or Windows NT environment; (B) that your software product does not substantially duplicate the capabilities of Microsoft Access or, in the reasonable opinion of Microsoft, compete with same; © to not use Microsoft’s name, logo, or trademarks to market your software product; (d) to include a valid copyright notice on your software product; and (e) to indemnify, hold harmless, and defend Microsoft and its suppliers from and against any claims or lawsuits, including attorneys’ fees, that arise or result from the use or distribution of your software product.
Unless your software product requires your customers to license Microsoft Access in order to operate, you may not reproduce or use any of the Run-Time Files for commercial distribution in conjunction with a general purpose word processing, spreadsheet, or database management software product, or an integrated work or product suite whose components include a general purpose word processing, spreadsheet, or database management software product except for the exclusive use of importing data to the various formats supported by Microsoft Access. Note: A product that includes limited word processing, spreadsheet, or database components along with other components which provide significant and primary value, such as an accounting product with limited spreadsheet capability, is not considered to be a “general purpose” product.
ه. Redistribution Requirements—Sample Code or Replication Manager Files. If you redistribute the Sample Code or Replication Manager Files, you agree: (a) to not use Microsoft’s name, logo, or trademarks to market your software product; (B) to include a valid copyright notice on your software product; and © to indemnify, hold harmless, and defend Microsoft and its suppliers from and against any claims or lawsuits, including attorneys’ fees, that arise or result from the use or distribution of your software product.
2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.
a. Academic Edition Software. If the SOFTWARE PRODUCT is identified as “Academic Edition” or “AE,” you must be a “Qualified Educational User” to use the SOFTWARE PRODUCT. If you are not a Qualified Educational User, you have no rights under this EULA. To determine whether you are a Qualified Educational User, please contact the Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399 or the Microsoft subsidiary serving your country.
b. Not for Resale Software. If the SOFTWARE PRODUCT is labeled “Not for Resale” or “NFR,” then, notwithstanding other sections of this EULA, you may not resell, or otherwise transfer for value, the SOFTWARE PRODUCT.
c. Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
d. Separation of Components. The SOFTWARE PRODUCT is licensed as a single product. Its component parts may not be separated for use on more than one computer.
e. Rental. You may not rent, lease, or lend the SOFTWARE PRODUCT.
f. Support Services. Microsoft may provide you with support services related to the SOFTWARE PRODUCT (“Support Services”). Use of Support Services is governed by the Microsoft policies and programs described in the user manual, in “online” documentation, and/or in other Microsoft-provided materials. Any supplemental software code provided to you as part of the Support Services shall be considered part of the SOFTWARE PRODUCT and subject to the terms and conditions of this EULA. With respect to technical information you provide to Microsoft as part of the Support Services, Microsoft may use such information for its business purposes, including for product support and development. Microsoft will not utilize such technical information in a form that personally identifies you.
g. Software Transfer. You may permanently transfer all of your rights under this EULA, provided you retain no copies, you transfer all of the SOFTWARE PRODUCT (including all component parts, the media and printed materials, any upgrades, this EULA, and, if applicable, the Certificate of Authenticity), and the recipient agrees to the terms of this EULA. If the SOFTWARE PRODUCT is an upgrade, any transfer must include all prior versions of the SOFTWARE PRODUCT.
h. Termination. Without prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE PRODUCT and all of its component parts.
3. UPGRADES. If the SOFTWARE PRODUCT is labeled as an upgrade, you must be properly licensed to use a product identified by Microsoft as being eligible for the upgrade in order to use the SOFTWARE PRODUCT. A SOFTWARE PRODUCT labeled as an upgrade replaces and/or supplements the product that formed the basis for your eligibility for the upgrade. You may use the resulting upgraded product only in accordance with the terms of this EULA. If the SOFTWARE PRODUCT is an upgrade of a component of a package of software programs that you licensed as a single product, the SOFTWARE PRODUCT may be used and transferred only as part of that single product package and may not be separated for use on more than one computer.
4. COPYRIGHT. All title and copyrights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and “applets” incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by Microsoft or its suppliers. The SOFTWARE PRODUCT is protected by copyright laws and international treaty provisions. Therefore, you must treat the SOFTWARE PRODUCT like any other copyrighted material except that you may install the SOFTWARE PRODUCT on a single computer provided you keep the original solely for backup or archival purposes. You may not copy the printed materials accompanying the SOFTWARE PRODUCT.
5. DUAL-MEDIA SOFTWARE. You may receive the SOFTWARE PRODUCT in more than one medium. Regardless of the type or size of medium you receive, you may use only one medium that is appropriate for your single computer. You may not use or install the other medium on another computer. You may not loan, rent, lease, or otherwise transfer the other medium to another user, except as part of the permanent transfer (as provided above) of the SOFTWARE PRODUCT.
6. U.S. GOVERNMENT RESTRICTED RIGHTS. The SOFTWARE PRODUCT and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph ©(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs ©(1) and (2) of the Commercial Computer Software—Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Microsoft Corporation/One Microsoft Way/Redmond, WA 98052-6399.
7. EXPORT RESTRICTIONS. You agree that neither you nor your customers intend to or will, directly or indirectly, export or transmit (i) the SOFTWARE or related documentation and technical data or (ii) your software product as described in Section 1(B) of this License (or any part thereof), or process, or service that is the direct product of the SOFTWARE, to any country to which such export or transmission is restricted by any applicable U.S. regulation or statute, without the prior written consent, if required, of the Bureau of Export Administration of the U.S. Department of Commerce, or such other governmental entity as may have jurisdiction over such export or transmission.
MISCELLANEOUS
If you acquired this product in the United States, this EULA is governed by the laws of the State of Washington.
If you acquired this product in Canada, this EULA is governed by the laws of the Province of Ontario, Canada. Each of the parties hereto irrevocably attorns to the jurisdiction of the courts of the Province of Ontario and further agrees to commence any litigation which may arise hereunder in the courts located in the Judicial District of York, Province of Ontario.
If this product was acquired outside the United States, then local law may apply.
Should you have any questions concerning this EULA, or if you desire to contact Microsoft for any reason, please contact the Microsoft subsidiary serving your country, or write: Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399.
LIMITED WARRANTY
LIMITED WARRANTY. Except with respect to the REDISTRIBUTABLES, which are provided “as is,” without warranty of any kind, Microsoft warrants that (a) the SOFTWARE PRODUCT will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of receipt, and (B) any Support Services provided by Microsoft shall be substantially as described in applicable written materials provided to you by Microsoft, and Microsoft support engineers will make commercially reasonable efforts to solve any problem issues. Some states and jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. To the extent allowed by applicable law, implied warranties on the SOFTWARE PRODUCT, if any, are limited to ninety (90) days.
CUSTOMER REMEDIES. Microsoft’s and its suppliers’ entire liability and your exclusive remedy shall be, at Microsoft’s option, either (a) return of the price paid, if any, or (B) repair or replacement of the SOFTWARE PRODUCT that does not meet Microsoft’s Limited Warranty and which is returned to Microsoft with a copy of your receipt. This Limited Warranty is void if failure of the SOFTWARE PRODUCT has resulted from accident, abuse, or misapplication. Any replacement SOFTWARE PRODUCT will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside the United States, neither these remedies nor any product support services offered by Microsoft are available without proof of purchase from an authorized international source.
NO OTHER WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND ITS SUPPLIERS DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, WITH REGARD TO THE SOFTWARE PRODUCT, AND THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHERS, WHICH VARY FROM STATE/JURISDICTION TO STATE/JURISDICTION.
LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE PRODUCT OR THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES, EVEN IF MICROSOFT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY CASE, MICROSOFT’S ENTIRE LIABILITY UNDER ANY PROVISION OF THIS EULA SHALL BE LIMITED TO THE GREATER OF THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE PRODUCT OR U.S.$5.00; PROVIDED, HOWEVER, IF YOU HAVE ENTERED INTO A MICROSOFT SUPPORT SERVICES AGREEMENT, MICROSOFT’S ENTIRE LIABILITY REGARDING SUPPORT SERVICES SHALL BE GOVERNED BY THE TERMS OF THAT AGREEMENT. BECAUSE SOME STATES AND JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
Si vous avez acquis votre produit Microsoft au CANADA, la garantie limitée suivante vous concerne :
GARANTIE LIMITÉE
GARANTIE LIMITÉE — Sauf pour celles du REDISTRIBUTABLES, qui sont fournies “comme telles,” sans acune garantie quelle qu’elle soit, Microsoft garantit que (a) la performance du LOGICIEL sera substantiellement en conformité avec la documentation qui accompagne le LOGICIEL, pour une période de quatre-vingt-dix (90) jours à compter de la date de réception ; et (B) tout support technique fourni par Microsoft sera substantiellement en conformité avec toute documentation afférente fournie par Microsoft et que les membres du support technique de Microsoft feront des efforts raisonnables pour résoudre toute difficulté technique découlant de l’utilisation du LOGICIEL. Certaines juridictions ne permettent pas de limiter dans le temps l’application de la présente garantie. Aussi, la limite stipulée ci-haut pourrait ne pas s’appliquer dans votre cas. Dans la mesure permise par la loi, toute garantie implicite portant sur le LOGICIEL, le cas échéant, est limitée à une période de quatre-vingt-dix (90) jours.
RECOURS DU CLIENT — La seule obligation de Microsoft et de ses fournisseurs et votre recours exclusif seront, au choix de Microsoft, soit (a) le remboursement du prix payé, si applicable, ou (B) la réparation ou le remplacement du LOGICIEL qui n’est pas conforme à la Garantie Limitée de Microsoft et qui est retourné à Microsoft avec une copie de votre reçu. Cette Garantie Limitée est nulle si le défaut du LOGICIEL est causé par un accident, un traitement abusif ou une mauvaise application. Tout LOGICIEL de remplacement sera garanti pour le reste de la période de garantie initiale ou pour trente (30) jours, selon la plus longue de ces périodes. A l’extérieur des Etats-Unis, aucun de ces recours non plus que le support technique offert par Microsoft ne sont disponibles sans une preuve d’achat provenant d’une source authorisée.
AUCUNE AUTRE GARANTIE — DANS LA MESURE PREVUE PAR LA LOI, MICROSOFT ET SES FOURNISSEURS EXCLUENT TOUTE AUTRE GARANTIE OU CONDITION, EXPRESSE OU IMPLICITE, Y COMPRIS MAIS NE SE LIMITANT PAS AUX GARANTIES OU CONDITIONS IMPLICITES DU CARACTERE ADEQUAT POUR LA COMMERCIALISATION OU UN USAGE PARTICULIER EN CE QUI CONCERNE LE LOGICIEL OU CONCERNANT LE TITRE , L’ABSENCE DE CONTREFAÅON DUDIT LOGICIEL, ET TOUTE DOCUMENTATION ECRITE QUI L’ACCOMPAGNE, AINSI QUE POUR TOUTE DISPOSITION CONCERNANT LE SUPORT TECHNIQUE OU LA FAÅON DONT CELUI-CI A ETE RENDU. CETTE GARANTIE LIMITEE VOUS ACCORDE DES DROITS JURIDIQUES SPECIFIQUES.
PAS DE RESPONSABILITE POUR LES DOMMAGES INDIRECTS — MICROSOFT OU SES FOURNISSEURS NE SERONT PAS RESPONSABLES EN AUCUNE CIRCONSTANCE POUR TOUT DOMMAGE SPECIAL, INCIDENT, INDIRECT, OU CONSEQUENT QUEL QU’IL SOIT (Y COMPRIS, SANS LIMITATION, LES DOMMAGES ENTRAINES PAR LA PERTE DE BENEFICES, L’INTERRUPTION DES ACTIVITES, LA PERTE D’INFORMATION OU TOUTE AUTRE PERTE PECUNIAIRE) DECOULANT DE L’UTILISATION OU DE L’IMPOSSIBILITE D’UTILISATION DE CE LOGICIEL AINSI QUE POUR TOUTE DISPOSITION CONCERNANT LE SUPORT TECHNIQUE OU LA FAÅON DONT CELUI-CI A ETE RENDU ET CE, MEME SI MICROSOFT A ETE AVISEE DE LA POSSIBILITE DE TELS DOMMAGES. LA RESPONSABILITE DE MICROSOFT EN VERTU DE TOUTE DISPOSITION DE CETTE CONVENTION NE POURRA EN AUCUN TEMPS EXCEDER LE PLUS ELEVE ENTRE I) LE MONTANT EFFECTIVEMENT PAYE PAR VOUS POUR LE LOGICIEL OU II) US$5.00. ADVENANT QUE VOUS AYEZ CONTRACTE PAR ENTENTE DISTINCTE AVEC MICROSOFT POUR UN SUPPORT TECHNIQUE ETENDU, VOUS SEREZ LIE PAR LES TERMES D’ UNE TELLE ENTENTE.
La présente Convention est régie par les lois de la province d’Ontario, Canada. Chacune des parties à la présente reconnaît irrévocablement la compétence des tribunaux de la province d’Ontario et consent à instituer tout litige qui pourrait découler de la présente auprès des tribunaux situés dans le district judiciaire de York, province d’Ontario.
Au cas où vous auriez des questions concernant cette licence ou que vous désiriez vous mettre en rapport avec Microsoft pour quelque raison que ce soit, veuillez contacter la succursale Microsoft desservant votre pays, dont l’adresse est fournie dans ce produit, ou écrivez à : Microsoft Sales Information Center, One Microsoft Way, Redmond, Washington 98052-6399.
أخي الكريم
للأسف هذا ليس كل شي عن البرنامج
هذه اتفاقية الترخيص لاستخدام البرنامج و الضمان بكل من الانجليزية و الفرنسية و لا يمكن معرفة معلومات منها لأنها صيغة عامة و لا تخص برنامج بعينه
اخوانى كيف اطلعكم على البرنامج علما انة ممكن ان تنصب علية برنامجك الذي عملة في اكسس او اي عمل في اورد بدون اوفست يشتغل على وندز واية اصدار
ارجو انتخبروني كيف اطلعكم لنستفيد الجميع من هذ البرنامج الرايع
والذي ماتتوقعة اخي ولكن اثبتلك اذا فهمة عملة وانا معرفتي في الغة قليلة جدا وشكر تعاونكم
أخي الكريم
نشكرك علي رغبتك فى افادتنا
من قائمة Help لمعظم البرامج يوجد تعرف للبرنامج (عادة تحت عنوان About أو version
انقل لنا المكتوب حرفيا
عموما هناك برامج تعمل setup ربما تقصد
setupFactory
أو
installationsheild
او
install-us
أو أرسل لي ملف الhelp أو ال Readme من ضمن الملفات الي بريدي
وان كانت الانجليزية أسهل لك فى التوضيح فى البريد فلا توجد مشكلة فى ذلك
و ان كان الملف غير ضخم أرجو ارساله لي علي البريد
و شكرا
Setup Wizard Overview اذا كانت هذي تكفي والا بلغني
See Also
The Setup Wizard helps you create a custom Setup program that quickly and easily installs your application. For help on the options in any page of the Setup Wizard, click the Help button on that page.
After you answer the Setup Wizard's questions, it copies files to a separate set of folders on your hard disk, called disk images, which contain the Setup program itself as well as your application and all the files needed to run it. You can then copy the disk images to floppy disks for distribution, or place them on a network drive or CD-ROM from which users can run the Setup program.
Depending on the options you choose when you run the Setup Wizard, your application's custom Setup program can:
· Copy your application's files to specified locations on a user's hard disk.
· Create Windows shortcuts that start your application or peripheral files, and specify various options used to open or run the files.
· Add Windows registry keys and entries for your application.
· Group files, shortcuts, and registry keys and entries into components that users can select.
· Install the run-time version of Microsoft Access so that users won't need to have Microsoft Access previously installed in order to run your application.
· Install other Microsoft Office components, such as Microsoft Graph 97, Microsoft Replication Manager, ISAM drivers used for accessing various data sources, and the files needed to use ODBCDirect .
· Run an application or open a file after the Setup program finishes installing your application.
Saving and Reloading Setup Wizard Settings
By default, the Setup Wizard assumes you're creating a Setup program for a new application. If you've previously run the Setup Wizard and have saved the setup options for your application, you can reuse the existing settings when you start the Setup Wizard. On the first page of the Setup Wizard, click the option to use previously saved setup options. When you click Next to move to the next page, the Setup Wizard asks you to specify the template file you saved when you previously ran the Setup Wizard.
If you use an existing template, you can keep or change any of the settings you specified previously.
Creating Setup Programs with Single or Multiple Components
Depending on your application's needs, you can create a Setup program that installs single or multiple components. A Setup program with a single component doesn't give users the option to choose which components to install. To create a Setup program with a single component, just assign all the files and other setup items for your application to the default Application component.
You can include additional components in a single-component Setup program, but keep them hidden from users. For example, you might want to hide a component to make sure that it is always installed. To hide a component, add the component and then clear its Display In Component List check box in the Components Builder dialog box or in the Reorder Components page in the Setup Wizard. The Setup program includes the component in the installation but doesn't display it in the component list.
You can include more than one component in your application. This can be useful if you have different levels of users, some of whom do not require certain components. For example, when you install Microsoft Office, you can choose to install or not to install a number of components, such as Microsoft Graph 97 or Help files containing advanced programming topics.
In a Setup program with multiple components, users can select the components they want to install on their systems by choosing the Custom option in the Setup program. When you specify files and other setup items in the Setup Wizard pages, you select a component that each item belongs to, and specify whether the item is required or if it can be left off users' hard disks to save space. A user can unselect a required file or other setup item when using the Custom setup option in the Setup program; however, the user will be warned that this component is vital to the application.
In addition to the Help topics available for each page in the Setup Wizard (which are available by clicking the Help button on the page), there are some general Help topics about the Setup Wizard that can help you with particular features of the Setup Wizard, or common problems encountered when using it. For information about using the Setup Wizard to distribute replicated applications, see Distributing Replicated Applications Using the Setup Wizard . For information about using the English Setup Wizard with a different language version of Microsoft Access, see Using the English Setup Wizard with a Different Language Version of Microsoft Access . For information about common problems encountered when using the Setup Wizard, see Avoiding or Solving the Most Common Problems Encountered When Using the Setup Wizard .
وهذا واعذرن لا اجيد الانجليزيةAvoiding or Solving the Most Common Problems Encountered When Using the Setup Wizard
See Also
This topic lists the most common problems encountered when using the Setup Wizard and describes how to avoid or solve them.
Setup Wizard Error Message Occurs When You Attempt to Create Disk Images for Your Application
You may see the following error message when you try to create disk images for your application using the Setup Wizard:
Setup Wizard
Permission Denied
After you see this error message, you'll see the error message "The creation of your custom Setup program was not completed successfully."
This error occurs if you specify a workgroup information (.mdw) file for your application that's the same workgroup information file being used for the current instance of Microsoft Access. You specify a workgroup information file on the Add Files page of the Setup Wizard, using the Set As Workgroup File check box.
To avoid this error message, create a copy of the workgroup information file, and use this copy as the workgroup information file for your application.
Note You will also see the same error message if you try to add any file to your custom application that's currently in use by Microsoft Access or another application.
"Object Error 325" Occurs While Your Custom Setup Program Is Running
To avoid this error, always change the version number of your application each time you change the files included in the Setup program. In addition, make sure you use a different name for each application you create.
Default Installation Folder for Your Application Is Always on Drive C
When a user sets up your application, your custom Setup program suggests a default folder for the application's installation. You set the default folder that's suggested on the Provide Application Details page of the Setup Wizard.
You can enter any folder path you want, but note that the custom Setup program will always suggest the first available hard drive, typically C:, as the root for this path. Your users can choose to use another location for the application's installation.
You Receive a Compile Error When You Run Your Run-Time Application
If your run-time application uses methods, properties, or functions in a referenced database, your application must include the referenced database, or you must remove the methods, properties, or functions from your run-time application.
You can check to see if your run-time application uses such methods, properties, or functions by running your application in full Microsoft Access. The References dialog box on the Tools menu lists any referenced databases. You can add such databases to your application's custom Setup program by using the Add Files page in the Setup Wizard.
Users Can't Run Microsoft Graph 97 from Your Run-Time Application
After uninstalling an Office application, users of your application may get an error message saying the application can't find the dynamic-link library (DLL) Mso97 when they try to run Graph from within your application. To correct this problem, they need to reinstall your application.
Users Can't Run Your Run-Time Application Without Connecting to a Network Server or Having a CD-ROM Available
If a user has installed Microsoft Office Professional 97 or Microsoft Access 97 on a network server or on a CD-ROM (that is, they don't have a full local version of Microsoft Access), installing your custom run-time application on their computer does not install a local version of Microsoft Access. So, in order to run your run-time application, the user must be connected to the network server or have the CD-ROM available.
To work around this problem, the user can uninstall both Microsoft Office Professional 97 or Microsoft Access 97 and your run-time application, then reinstall them, making sure to install your run-time application first.
Database (.Mdb) Files No Longer Automatically Open in Microsoft Access
After uninstalling Microsoft Access, users of your run-time application may find that .mdb files no longer automatically open in Microsoft Access even though the run-time version of Microsoft Access is still installed on their machines.
To work around this problem, users can either reinstall your application or manually add an association between .mdb files and Msaccess.exe. To keep this problem from occurring, make sure you include "msaccess.exe" in the command line for the shortcut that opens your application (for example, "Msaccess.exe" /runtime "$(FilePath)MyApp.mdb" ).
Users Can't Open the Custom Help File for Your Run-Time Application
If users of your run-time application are prompted to open the Microsoft Access Help file instead of your custom Help file, you need to create and set the AppHelpFile key in the Windows registry under the Run-Time Options key. For more information about creating these keys, see Microsoft Access Run-Time Option Settings .
You Must Use Either Full or No Filename Extensions for Compressed Files Included in Your Application
If you create disk images for your application in compressed format (you select 1.44-MB Disks or Compressed Network or CD Setup on the Specify Disk Image Options page in the Setup Wizard), you must either use full three-letter filename extensions (for example, MyApp.mdb) or use no extension (for example, Readme) for any files you specify for your application. If you don't, you'll get a "Setup could not open the file ' filename ' " error when you are running the custom Setup program for your application.
You Must Open Disk Image Folders and Highlight All the Files When Copying Your Application's Files to Disks
When copying files from the disk images for your application to 1.44-MB disks, you must open each folder in the disk images set and highlight all the files in the folder before copying its files to the disks. The default folder for your disk images is c:Program FilesMicrosoft OfficeODEToolsSetup WizardImagesDisks. This folder will contain folders named Disk1, Disk2, and so forth. To copy the files in the Disk1 folder, open this folder and highlight all the files before copying the folder to floppy disks. Repeat this procedure for all the other disk folders.
You should also make sure the .dll files for your application are visible in the disk images before you copy the files. By default, Microsoft Windows 95 hides .dll files in Windows Explorer.
Creating Front-End/Back-End Applications
The Setup Wizard doesn't support administrative installations using the /a switch when installing Microsoft Access run-time applications. That is, you can't install a main application containing all of your data and database objects on a server, and then from that server installation install "front-end" applications containing just the queries, forms, reports, macros, and modules on workstation computers.
To simulate this functionality, you should create two applications. Create one application that contains all of the data and database objects you want in your application (this is called a "main" or "back-end" application). Create another application that contains just the queries, forms, reports, macros, and modules from the main application (this is called a "front-end" application). In this application, include links to the data in the main application. Use the Setup Wizard to create a custom Setup program containing two components. One component contains the main application. You can specify that this component is only available in a Complete or Custom installation. The second component, available in a Typical installation, contains the front-end application. Administrators can then run your custom Setup program and install the main application on a network server. Users can run your custom Setup program and install the front-end application on a local computer.
For more information about creating front-end and back-end applications, see Split an existing database between its data and its objects .
You Should Specify a Unique Application Name, Version Number, and Destination Folder for Each Application You Create
When you create an application's custom Setup program using the Setup Wizard, be sure to specify a unique application name, version number, and destination folder for the application in the Provide Application Details page of the Setup Wizard. For example, it's usually a bad idea to install an application in the same folder as Microsoft Access; file names in your application could conflict with existing Microsoft Access filenames.
Adding Required Redistributable Components to Your Application
See Also
You can include a number of redistributable components in your application. To select these components, use the Add Redistributable Components page in the Setup Wizard. Each of these components requires one or more Microsoft Office or Microsoft Access files. Not all of these files are installed by default when you install Microsoft Office 97, Professional Edition or Microsoft Access 97 and the Microsoft Office 97, Developer Edition (ODE) Tools. Some of these files are included in a Typical setup of Office Professional or Microsoft Access, or a Complete setup of ODE Tools, but others are only available from a Custom setup or from the Office 97 ValuPack. If you're creating a custom Setup program by using the Setup Wizard and want to include a redistributable component in your application, you must be sure that the file or files required for this component are present on your computer. You may need to re-run the Setup programs for Office Professional, Microsoft Access, or ODE Tools, or get the desired files from the ValuPack.
The table below shows which Setup program provides the redistributable components listed on the Add Redistributable Components page of the Setup Wizard. To install a component that's available from the Office Professional or Microsoft Access Setup program, run the Setup program and click the Add/Remove button. Then select the option shown in the table below (in some cases, you'll need to click the Change Option button and make an additional selection; in other cases you'll need to make an additional selection after this and click the Change Option button again). Select the component you want to include in your application, return to the Setup screen listing the components you can install or uninstall (if necessary), and click the Continue button to complete the Setup program.
Some components are available from the ODE Tools Setup program. Run the Setup program, and click the Add/Remove button. Select the component you want and click the Continue button. Note that all of the components included with the ODE Tools Setup program are installed by default when you run a Complete setup.
Some components are only included in the Office 97 ValuPack (additionally, the ValuPack includes all of the database drivers available from Microsoft Access Setup). For information about installing components from the ValuPack, see About the Office 97 ValuPack .
In the following table, "Setup program" refers to the Office Professional or Microsoft Access Setup program.
Redistributable component Available from
Microsoft Access Run-Time Version Any installation of Microsoft Access or Office Professional, plus an installation of ODE Tools
Microsoft Excel ISAM Setup program: Select Data Access , then Database Drivers , then Microsoft Excel Driver
Paradox ISAM ValuPack: Available from the Data Access Pak folder
Text & HTML ISAM Setup program: Select Data Access , then Database Drivers , then Text And HTML Driver
Lotus ISAM ValuPack: Available from the Data Access Pak folder
Xbase ISAM Setup program: Select Data Access , then Database Drivers , then dBASE And Microsoft FoxPro Drivers
Microsoft Graph 97 Run-Time Version ODE Tools Setup program: Select Microsoft Graph 97 Run-Time Version (installed by default)
Workgroup Administrator Automatically installed when you install Microsoft Access
Microsoft Replication Manager ODE Tools Setup program: Select Microsoft Replication Manager (installed by default)
ODBC Support with SQL Server Setup program: Select Data Access , then Database Drivers , then Microsoft SQL Server Driver
Microsoft Exchange/Outlook ISAM ValuPack: Available from the Data Access Pak folder
ODBCDirect Automatically installed when you install Microsoft Access Note If you include the ODBCDirect component, you also have to include the ODBC Support with SQL Server component, or the user has to already have ODBC installed on his or her machine.
هذا الموضوع مغلق.