الفريق العربي للبرمجةأرشيف المنتديات · 2000 – 2023
نسخة أرشيفية للقراءة فقط — التسجيل والمشاركة مغلقان، والمحتوى محفوظ كما كان.

Tips in MS Access

مغلق
بدأه فيصل الحربي في 4 أغسطس 2004 · 2 رد · 680 مشاهدة · في قواعد بيانات Microsoft Access
مشاركة: واتساب X فيسبوك تيليجرام
#1 صاحب الموضوع

بسم الله الرحمن الرحيم

السلام عليكم ورحمة الله وبركاته

تصلني على بريدي رسائل خاصة في طرق تحسين اداء قواعد البيانات من موقع إنجليزي .

سأضعها هنا لمن يرغب بالاستفادة منها

====

********** THE TIP **********

Use UNC paths to avoid linked table problems (Access 97/2000/2002)

Access developers commonly use a split application design model.
In a split application, data tables are stored in a separate file
from the forms, reports, and other objects that comprise the
complete application. When creating a split application, or any
database that links to external files, be careful to avoid a
common source of problems--mapped drive letters.

The ability to map network folders to a drive letter provides
convenience to users, but cause headaches for developers. For
example, your PC may be configured to map the E: drive to a
particular folder on your network. However, a co-worker's PC
might have the E: drive assigned to a DVD-ROM drive. If you
design a split application that links to a file stored in what
appears to be your E: drive, the application won't work correctly
when your coworker uses it.

The solution is to use UNC paths instead of drive letters when
setting the path to a particular file. Don't use the traditional
path format, which is as follows:

<drive letter>:\<folder name>\<filename>

Instead, use a path in the following format:

\\<server name>\<folder name>\<filename>

Since the computer where the file resides defines the server
name used in a UNC path, the value is the same regardless of what
computer you're using to connect to the server.

=========

هي باللغة الانجليزية ولا يوجد عندي متسع من الوقت لترجمتها .

===

صورة
صورة

حسابي في الفيس بوك
http://goo.gl/XIzwL

حسابي في تويتر
http://goo.gl/6p4e3

 

 
 
#2

لك كل الشكر أستاذ فيصل .. رغم أني لن استفيد منها شيئ وهي باللغة الإنجليزية .

#3

بسم الله الرحمن الرحيم

السلام عليكم ورحمة الله وبركاته

كان الله في عونك أخي فهد

ويا حبذا من يقوم بالترجمة :

********** THE TIP **********

Creating record-level validation rules (Access 97/2000/2002)

We've previously discussed how you can assign validation rules
to a field or form control to ensure that its entry conforms to
particular criteria. In addition to this, you can set
record-level validation rules that must be met before a record
can be saved. Unlike field-level rules, which depend solely on
the value in that specific field, a record-level validation rule
is based on data from multiple fields within the table. Access
only allows one record-level validation rule per table, but you
can apply more than one condition by building an expression using
an And or an Or operator.

To create a record-level validation rule, open the appropriate
table in Design view. Then, choose View | Properties from the
menu bar. Enter your validation expression in the Validation Rule
text box. For example, you might use an expression such as the following:

[Hours] >=30 Or ([Hours]< 30 And [Health]=False)

This expression requires that the Hours value is greater than or
equal to 30 or, if it's less than 30, that the Health field
equals False. If both of the conditions being tested evaluate to
a False result, that record can't be saved. To display a custom
message to the user when the entry violates the validation rule,
enter an appropriate prompt in the Validation Text property's
text box.

====

صورة
صورة

حسابي في الفيس بوك
http://goo.gl/XIzwL

حسابي في تويتر
http://goo.gl/6p4e3

 

 
 

هذا الموضوع مغلق.

مواضيع مشابهة