Avery template not found

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Avery template not found

Pat Sheldon
Would anyone know how to  create a template for an Avery product that
is not listed within FMP 6, specifically Business Cards 8376.  I am
running Mac OS 10.3.9.  Am trying to make small labels for the cheese
in my shop. Each cheese has a record, etc etc.
Thanks, Pat






Pat Sheldon
Sheldon Farms Market
4363 Rte 22
Salem NY 12865

(518) 854-7847

Open May -  October, Seven days
Famous Sheldon sweet corn and everything else for a fresh, wonderful
meal.
On May 19, 2005, at 4:06 AM, <[hidden email]> wrote:

>          Digest #830
>
>  1) FM7 Color/Container Oddity
>     by Derrick Fogle <[hidden email]>
>  2) Globals in FM7
>     by Derrick Fogle <[hidden email]>
>  3) Re: Globals in FM7
>     by Fletcher Sandbeck <[hidden email]>
>  4) Re: Globals in FM7
>     by Ross Dickson <[hidden email]>
>  5) validating against itself
>     by Donnie Mayes <[hidden email]>
>  6) Re: Globals in FM7
>     by Derrick Fogle <[hidden email]>
>  7) Re: Globals in FM7
>     by "G. Pupita" <[hidden email]>
>  8) Re: Globals in FM7
>     by "Derrick Fogle" <[hidden email]>
>  9) Re: validating against itself
>     by Jim Main <[hidden email]>
> 10) Re: Globals in FM7
>     by Jim Main <[hidden email]>
>
> This digest is sent to you because you are subscribed to
>   the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> To switch to the FEED mode, E-mail to <[hidden email]>
> Send administrative queries to  <[hidden email]>
>
>
> ----------------------------------------------------------------------
>
> Message-Id: <[hidden email]>
> From: Derrick Fogle <[hidden email]>
> Subject: FM7 Color/Container Oddity
> Date: Wed, 18 May 2005 09:10:26 -0500
>
> Running FMD7 v3 on OSX 10.4.1
>
> I was setting up a bunch of global color containers, and while I was
> working on pasting blocks of colors into the graphics containers I
> ran across this usually-duplicatable oddity:
>
> If I copy a color block in layout mode (made with the rectangle tool,
> fill=color, line=none), and end up changing the layout in any way
> (causing me to have to accept or reject layout changes when I switch
> to browse mode), the color that pastes into the container is *often*
> much lighter than the color that I copied. Not every single time, but
> probably more than 50% of the time.
>
> If I don't change the layout in any way, the color that pastes into
> the container is always the same as the color I copied.
>
> Has anyone else noticed this?
>
> Derrick Fogle
> [hidden email]
>
>
>
> ------------------------------
>
> Message-Id: <[hidden email]>
> From: Derrick Fogle <[hidden email]>
> Subject: Globals in FM7
> Date: Wed, 18 May 2005 12:27:58 -0500
>
> Is there any way to really change the value of a global on the server
> in FMS7A so that it 'sticks' and starts showing up in all the other
> clients?
>
> Derrick Fogle
> [hidden email]
>
>
>
> ------------------------------
>
> Date: Wed, 18 May 2005 10:52:55 -0700
> From: Fletcher Sandbeck <[hidden email]>
> Subject: Re: Globals in FM7
> Message-ID:
> <r02010500-1041-AA50725CC7C511D9B5EC000393D5FB70@[192.168.0.103]>
>
> On 5/18/05 at 12:27 PM by [hidden email] (Derrick Fogle):
>
>> Is there any way to really change the value of a global on the server
>> =20
>> in FMS7A so that it 'sticks' and starts showing up in all the other
>> =20
>> clients?
>
> I don't know a specific answer to this question, but what I've found
> useful=
>  in a complex solution is to create a "Global" database that had a
> single r=
> ecord in it.  The record is recreated with default values at startup
> if it =
> does not exist.  The record has a literal in a keyfield and the same
> litera=
> l is put in a field in each database that needs to use the globals.  
> These =
> literals are used to create a relationship with the Global database.  
> Then,=
>  I can call globals from any database that needs them as related
> fields "Gl=
> obal::name".
>
> I would hope FM7 would make these kinds of workarounds unnecessary,
> but if =
> not this method would still probably work fine.
>
> [fletcher]
> --=20
> =46letcher Sandbeck                         [hidden email]
> Lasso Product Specialist              [hidden email]
> OmniPilot, Software Inc.                http://www.omnipilot.com
>
> ------------------------------
>
> Message-ID: <[hidden email]>
> Date: Wed, 18 May 2005 15:25:51 -0400
> From: Ross Dickson <[hidden email]>
> Subject: Re: Globals in FM7
>
> Derrick
> Further to Fletcher's comments, globals are still local in 7, so those
> fields that I want to have and keep the same values for all users, I
> put
> as regular fields, not as globals, into a one-record table, which can
> be
> related, if required, to other tables. All the global fields which
> users
> and scripts might need are kept in another zero record table, called
> for
> convenience sake, Globals.
>
> Ross
>
> Fletcher Sandbeck wrote:
>> On 5/18/05 at 12:27 PM by [hidden email] (Derrick Fogle):
>>
>>
>>> Is there any way to really change the value of a global on the server
>>> in FMS7A so that it 'sticks' and starts showing up in all the other
>>> clients?
>>
>>
>> I don't know a specific answer to this question, but what I've found
> useful in a complex solution is to create a "Global" database that had
> a single record in it.  The record is recreated with default values at
> startup if it does not exist.  The record has a literal in a keyfield
> and the same literal is put in a field in each database that needs to
> use the globals.  These literals are used to create a relationship with
> the Global database.  Then, I can call globals from any database that
> needs them as related fields "Global::name".
>>
>> I would hope FM7 would make these kinds of workarounds unnecessary,
> but if not this method would still probably work fine.
>>
>> [fletcher]
>
> ------------------------------
>
> Message-Id: <[hidden email]>
> Date: Wed, 18 May 2005 15:45:26 -0500
> From: Donnie Mayes <[hidden email]>
> Subject: validating against itself
>
> Greetings;
>
> I have a field that marks an employee either Active or Inactive.  Once
> Inactive, I have locked them out of changing the Hire/Exit date with
> this
> Validation calculation:  EXIT DATE = STATUS <> "InActive".  They can
> not
> override this error message.
>
> We don't want them changing back the Status back to Active so they're
> able
> to change the date either, but when I try that calculation, once I
> change
> it to Inactive, it won't let me do anything.  I can't create a new
> record,
> do any finds, or anything on it.
>
> It is stuck there in limbo.  Is there a work around for this?
>
> We also have in big red letters, Inactive Employee Record come up when
> they
> change it to Inactive.  I think I remember seeing some newsletter
> where you
> could make text blink, but I can't find where it was.
>
> Any suggestions would be greatly appreciated.
>
> Thank you.
>
> Don Mayes
>
>
> ------------------------------
>
> Message-Id: <[hidden email]>
> From: Derrick Fogle <[hidden email]>
> Subject: Re: Globals in FM7
> Date: Wed, 18 May 2005 15:58:06 -0500
>
> Actually, in FM7 you need a different TO to the globals table from
> each other table, don't you?
>
> I'm actually in favor, generally, of having a "globals" table in FM7,
> rather than using globals for that kind of storage. I'm just having
> trouble wrapping my head around the "Yet Another Table Occurrence" -
> not so much conceptually, but from a standpoint of visual clutter in
> the relationship graph. But also because I really do need to remember
> a dozen different TO names for what's essentially the same thing.
>
> I was trying to 'flatten out' a relationship graph, combining the
> globals file with a user file that I've got to hook up to just about
> every other table anyway. That's when I ran into the fact that I had
> to close the files on the server and open them directly to 'set'
> global fields in the user table that used to be stored fields in the
> globals table.
>
> Derrick Fogle
> [hidden email]
>
>
> On May 18, 2005, at 12:52 PM, Fletcher Sandbeck wrote:
>
>> Then, I can call globals from any database that needs them as
>> related fields "Global::name".
>
>
> ------------------------------
>
> Message-Id: <[hidden email]>
> From: "G. Pupita" <[hidden email]>
> Subject: Re: Globals in FM7
> Date: Wed, 18 May 2005 23:42:45 +0200
>
> Hi  Derrick
>
>> Actually, in FM7 you need a different TO to the globals table from
>> each other table, don't you?
> Not really, global fields can be accessed even without having a
> relationship to the globals table ...
>
> Ciao
> G. Pupita
> Certified FileMaker 7 Developer
>
> ------------------------------
>
> From: "Derrick Fogle" <[hidden email]>
> Subject: RE: Globals in FM7
> Date: Wed, 18 May 2005 18:07:29 -0500
> Message-ID: <[hidden email]>
>
> For global fields, you're correct, but that's not what I was commenting
> about. My comment was directed at using a regular field in a
> single-record
> 'globals' table.
>
> If you use the globals, you can't change the value of a global field
> on the
> server while the database is being hosted by a server. If you use the
> single-record globals table, you can change the value of a field and
> have
> them 'stick' even when it's being hosted by the server, but to get to
> it you
> also need a T.O. Or wait, even better yet a whole set of shadow global
> fields so you can also write a script to copy the stored local
> changeable/savable field data to the global fields so you have the
> best of
> both worlds!
>
> There's reasons and uses for both a 'globals' table and actual global
> fields.
>
> Derrick Fogle
> fogles.net consulting
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On
> Behalf
> Of G. Pupita
> Sent: Wednesday, May 18, 2005 4:43 PM
> To: [hidden email]
> Subject: Re: Globals in FM7
>
> Hi  Derrick
>
>> Actually, in FM7 you need a different TO to the globals table from
>> each other table, don't you?
> Not really, global fields can be accessed even without having a
> relationship to the globals table ...
>
> Ciao
> G. Pupita
> Certified FileMaker 7 Developer
>
> --
> ------------------------------
> This list is a free service of OmniPilot Software, Inc.
> http://www.omnipilot.com/
> Search the list archives:
> http://www.listsearch.com/filemakerprotalk.lasso
> Manage your subscription:
> http://www.listsearch.com/filemakerprotalk.lasso?manage
>
>
> ------------------------------
>
> Message-Id: <[hidden email]>
> From: Jim Main <[hidden email]>
> Subject: Re: validating against itself
> Date: Wed, 18 May 2005 17:05:34 -0700
>
> It sounds like you want conditional editing of the record, using
> Account Privileges?
>
> Using Filemaker 7:
> Select "Define: Accounts & Privileges" from the menu. Select the
> "Privilege Sets" tab, and Edit the Privilege Set you're restricting.
> Under "Data Access and Design, Records" set it to "Custom privileges".
> Highlight the Employee table, and under "Set Privileges, Edit" change
> to "Limited". You'll then be able to enter a validation calculation,
> like "Status <> "InActive". This will protect the entire record from
> modification once it's set to inactive, without restricting creating or
> deleting records.
>
> On May 18, 2005, at 1:45 PM, Donnie Mayes wrote:
>
>> Greetings;
>>
>> I have a field that marks an employee either Active or Inactive.  Once
>> Inactive, I have locked them out of changing the Hire/Exit date with
>> this Validation calculation:  EXIT DATE = STATUS <> "InActive".  They
>> can not override this error message.
>>
>> We don't want them changing back the Status back to Active so they're
>> able to change the date either, but when I try that calculation, once
>> I change it to Inactive, it won't let me do anything.  I can't create
>> a new record, do any finds, or anything on it.
>>
>> It is stuck there in limbo.  Is there a work around for this?
>>
>> We also have in big red letters, Inactive Employee Record come up when
>> they change it to Inactive.  I think I remember seeing some newsletter
>> where you could make text blink, but I can't find where it was.
>>
>> Any suggestions would be greatly appreciated.
>>
>> Thank you.
>>
>> Don Mayes
>>
>
> Jim Main
> -------------------------------------------
> 619-948-5293
> [hidden email]
> -------------------------------------------
>
>
> ------------------------------
>
> Message-Id: <[hidden email]>
> From: Jim Main <[hidden email]>
> Subject: Re: Globals in FM7
> Date: Wed, 18 May 2005 17:24:32 -0700
>
> It appears the pre FMP7 trick of entering 'Define Fields' no longer
> sets the server globals to the client's values. However, if you want to
> blank out global fields that have values on server, you can from a
> client switch them to non-global, then back to global fields, wiping
> them out.
>
> I personally use an openning script that initially sets all global
> values I want throughout the system from nonglobal fields into idental
> global fields. Then I don't need to worry about relationships between
> each TO and the global fields.
>
> On May 18, 2005, at 10:27 AM, Derrick Fogle wrote:
>
>> Is there any way to really change the value of a global on the server
>> in FMS7A so that it 'sticks' and starts showing up in all the other
>> clients?
>>
>> Derrick Fogle
>> [hidden email]
>>
>
> Jim Main
> -------------------------------------------
> 619-948-5293
> [hidden email]
> -------------------------------------------
>
>
> ------------------------------
>
> End of  Digest #830
> *******************
>


--
------------------------------
This list is a free service of OmniPilot Software, Inc.  
http://www.omnipilot.com/
Search the list archives:  
http://www.listsearch.com/filemakerprotalk.lasso
Manage your subscription:  
http://www.listsearch.com/filemakerprotalk.lasso?manage
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Avery template not found

Elizabeth Burns
>Hi Pat,

You can define a new layout and specify labels with custom
measurements.   Usually the box will have the dimensions of the
label, which you can then enter into FMP.  You should then be all set
up!

Hope this helps,
Elizabeth

>Would anyone know how to  create a template for an Avery product
>that is not listed within FMP 6, specifically Business Cards 8376.
>I am running Mac OS 10.3.9.  Am trying to make small labels for the
>cheese in my shop. Each cheese has a record, etc etc.
>Thanks, Pat
>
>
>
>
>
>
>Pat Sheldon
>Sheldon Farms Market
>4363 Rte 22
>Salem NY 12865
>
>(518) 854-7847
>
>Open May -  October, Seven days
>Famous Sheldon sweet corn and everything else for a fresh, wonderful meal.
>On May 19, 2005, at 4:06 AM, <[hidden email]> wrote:
>
>>          Digest #830
>>
>>  1) FM7 Color/Container Oddity
>>     by Derrick Fogle <[hidden email]>
>>  2) Globals in FM7
>>     by Derrick Fogle <[hidden email]>
>>  3) Re: Globals in FM7
>>     by Fletcher Sandbeck <[hidden email]>
>>  4) Re: Globals in FM7
>>     by Ross Dickson <[hidden email]>
>>  5) validating against itself
>>     by Donnie Mayes <[hidden email]>
>>  6) Re: Globals in FM7
>>     by Derrick Fogle <[hidden email]>
>>  7) Re: Globals in FM7
>>     by "G. Pupita" <[hidden email]>
>>  8) Re: Globals in FM7
>>     by "Derrick Fogle" <[hidden email]>
>>  9) Re: validating against itself
>>     by Jim Main <[hidden email]>
>>10) Re: Globals in FM7
>>     by Jim Main <[hidden email]>
>>
>>This digest is sent to you because you are subscribed to
>>   the mailing list <[hidden email]>.
>>To unsubscribe, E-mail to: <[hidden email]>
>>To switch to the FEED mode, E-mail to <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>>
>>
>>----------------------------------------------------------------------
>>
>>Message-Id: <[hidden email]>
>>From: Derrick Fogle <[hidden email]>
>>Subject: FM7 Color/Container Oddity
>>Date: Wed, 18 May 2005 09:10:26 -0500
>>
>>Running FMD7 v3 on OSX 10.4.1
>>
>>I was setting up a bunch of global color containers, and while I was
>>working on pasting blocks of colors into the graphics containers I
>>ran across this usually-duplicatable oddity:
>>
>>If I copy a color block in layout mode (made with the rectangle tool,
>>fill=color, line=none), and end up changing the layout in any way
>>(causing me to have to accept or reject layout changes when I switch
>>to browse mode), the color that pastes into the container is *often*
>>much lighter than the color that I copied. Not every single time, but
>>probably more than 50% of the time.
>>
>>If I don't change the layout in any way, the color that pastes into
>>the container is always the same as the color I copied.
>>
>>Has anyone else noticed this?
>>
>>Derrick Fogle
>>[hidden email]
>>
>>
>>
>>------------------------------
>>
>>Message-Id: <[hidden email]>
>>From: Derrick Fogle <[hidden email]>
>>Subject: Globals in FM7
>>Date: Wed, 18 May 2005 12:27:58 -0500
>>
>>Is there any way to really change the value of a global on the server
>>in FMS7A so that it 'sticks' and starts showing up in all the other
>>clients?
>>
>>Derrick Fogle
>>[hidden email]
>>
>>
>>
>>------------------------------
>>
>>Date: Wed, 18 May 2005 10:52:55 -0700
>>From: Fletcher Sandbeck <[hidden email]>
>>Subject: Re: Globals in FM7
>>Message-ID: <r02010500-1041-AA50725CC7C511D9B5EC000393D5FB70@[192.168.0.103]>
>>
>>On 5/18/05 at 12:27 PM by [hidden email] (Derrick Fogle):
>>
>>>Is there any way to really change the value of a global on the server =20
>>>in FMS7A so that it 'sticks' and starts showing up in all the other =20
>>>clients?
>>
>>I don't know a specific answer to this question, but what I've found useful=
>>  in a complex solution is to create a "Global" database that had a single r=
>>ecord in it.  The record is recreated with default values at startup if it =
>>does not exist.  The record has a literal in a keyfield and the same litera=
>>l is put in a field in each database that needs to use the globals.  These =
>>literals are used to create a relationship with the Global database.  Then,=
>>  I can call globals from any database that needs them as related fields "Gl=
>>obal::name".
>>
>>I would hope FM7 would make these kinds of workarounds unnecessary, but if =
>>not this method would still probably work fine.
>>
>>[fletcher]
>>--=20
>>=46letcher Sandbeck                         [hidden email]
>>Lasso Product Specialist              [hidden email]
>>OmniPilot, Software Inc.                http://www.omnipilot.com
>>
>>------------------------------
>>
>>Message-ID: <[hidden email]>
>>Date: Wed, 18 May 2005 15:25:51 -0400
>>From: Ross Dickson <[hidden email]>
>>Subject: Re: Globals in FM7
>>
>>Derrick
>>Further to Fletcher's comments, globals are still local in 7, so those
>>fields that I want to have and keep the same values for all users, I put
>>as regular fields, not as globals, into a one-record table, which can be
>>related, if required, to other tables. All the global fields which users
>>and scripts might need are kept in another zero record table, called for
>>convenience sake, Globals.
>>
>>Ross
>>
>>Fletcher Sandbeck wrote:
>>>On 5/18/05 at 12:27 PM by [hidden email] (Derrick Fogle):
>>>
>>>>Is there any way to really change the value of a global on the server
>>>>in FMS7A so that it 'sticks' and starts showing up in all the other
>>>>clients?
>>>
>>>
>>>I don't know a specific answer to this question, but what I've found
>>useful in a complex solution is to create a "Global" database that had
>>a single record in it.  The record is recreated with default values at
>>startup if it does not exist.  The record has a literal in a keyfield
>>and the same literal is put in a field in each database that needs to
>>use the globals.  These literals are used to create a relationship with
>>the Global database.  Then, I can call globals from any database that
>>needs them as related fields "Global::name".
>>>
>>>I would hope FM7 would make these kinds of workarounds unnecessary,
>>but if not this method would still probably work fine.
>>>
>>>[fletcher]
>>
>>------------------------------
>>
>>Message-Id: <[hidden email]>
>>Date: Wed, 18 May 2005 15:45:26 -0500
>>From: Donnie Mayes <[hidden email]>
>>Subject: validating against itself
>>
>>Greetings;
>>
>>I have a field that marks an employee either Active or Inactive.  Once
>>Inactive, I have locked them out of changing the Hire/Exit date with this
>>Validation calculation:  EXIT DATE = STATUS <> "InActive".  They can not
>>override this error message.
>>
>>We don't want them changing back the Status back to Active so they're able
>>to change the date either, but when I try that calculation, once I change
>>it to Inactive, it won't let me do anything.  I can't create a new record,
>>do any finds, or anything on it.
>>
>>It is stuck there in limbo.  Is there a work around for this?
>>
>>We also have in big red letters, Inactive Employee Record come up when they
>>change it to Inactive.  I think I remember seeing some newsletter where you
>>could make text blink, but I can't find where it was.
>>
>>Any suggestions would be greatly appreciated.
>>
>>Thank you.
>>
>>Don Mayes
>>
>>
>>------------------------------
>>
>>Message-Id: <[hidden email]>
>>From: Derrick Fogle <[hidden email]>
>>Subject: Re: Globals in FM7
>>Date: Wed, 18 May 2005 15:58:06 -0500
>>
>>Actually, in FM7 you need a different TO to the globals table from
>>each other table, don't you?
>>
>>I'm actually in favor, generally, of having a "globals" table in FM7,
>>rather than using globals for that kind of storage. I'm just having
>>trouble wrapping my head around the "Yet Another Table Occurrence" -
>>not so much conceptually, but from a standpoint of visual clutter in
>>the relationship graph. But also because I really do need to remember
>>a dozen different TO names for what's essentially the same thing.
>>
>>I was trying to 'flatten out' a relationship graph, combining the
>>globals file with a user file that I've got to hook up to just about
>>every other table anyway. That's when I ran into the fact that I had
>>to close the files on the server and open them directly to 'set'
>>global fields in the user table that used to be stored fields in the
>>globals table.
>>
>>Derrick Fogle
>>[hidden email]
>>
>>
>>On May 18, 2005, at 12:52 PM, Fletcher Sandbeck wrote:
>>
>>>Then, I can call globals from any database that needs them as
>>>related fields "Global::name".
>>
>>
>>------------------------------
>>
>>Message-Id: <[hidden email]>
>>From: "G. Pupita" <[hidden email]>
>>Subject: Re: Globals in FM7
>>Date: Wed, 18 May 2005 23:42:45 +0200
>>
>>Hi  Derrick
>>
>>>Actually, in FM7 you need a different TO to the globals table from
>>>each other table, don't you?
>>Not really, global fields can be accessed even without having a
>>relationship to the globals table ...
>>
>>Ciao
>>G. Pupita
>>Certified FileMaker 7 Developer
>>
>>------------------------------
>>
>>From: "Derrick Fogle" <[hidden email]>
>>Subject: RE: Globals in FM7
>>Date: Wed, 18 May 2005 18:07:29 -0500
>>Message-ID: <[hidden email]>
>>
>>For global fields, you're correct, but that's not what I was commenting
>>about. My comment was directed at using a regular field in a single-record
>>'globals' table.
>>
>>If you use the globals, you can't change the value of a global field on the
>>server while the database is being hosted by a server. If you use the
>>single-record globals table, you can change the value of a field and have
>>them 'stick' even when it's being hosted by the server, but to get to it you
>>also need a T.O. Or wait, even better yet a whole set of shadow global
>>fields so you can also write a script to copy the stored local
>>changeable/savable field data to the global fields so you have the best of
>>both worlds!
>>
>>There's reasons and uses for both a 'globals' table and actual global
>>fields.
>>
>>Derrick Fogle
>>fogles.net consulting
>>
>>-----Original Message-----
>>From: [hidden email] [mailto:[hidden email]] On Behalf
>>Of G. Pupita
>>Sent: Wednesday, May 18, 2005 4:43 PM
>>To: [hidden email]
>>Subject: Re: Globals in FM7
>>
>>Hi  Derrick
>>
>>>Actually, in FM7 you need a different TO to the globals table from
>>>each other table, don't you?
>>Not really, global fields can be accessed even without having a
>>relationship to the globals table ...
>>
>>Ciao
>>G. Pupita
>>Certified FileMaker 7 Developer
>>
>>--
>>------------------------------
>>This list is a free service of OmniPilot Software, Inc.
>>http://www.omnipilot.com/
>>Search the list archives:
>>http://www.listsearch.com/filemakerprotalk.lasso
>>Manage your subscription:
>>http://www.listsearch.com/filemakerprotalk.lasso?manage
>>
>>
>>------------------------------
>>
>>Message-Id: <[hidden email]>
>>From: Jim Main <[hidden email]>
>>Subject: Re: validating against itself
>>Date: Wed, 18 May 2005 17:05:34 -0700
>>
>>It sounds like you want conditional editing of the record, using
>>Account Privileges?
>>
>>Using Filemaker 7:
>>Select "Define: Accounts & Privileges" from the menu. Select the
>>"Privilege Sets" tab, and Edit the Privilege Set you're restricting.
>>Under "Data Access and Design, Records" set it to "Custom privileges".
>>Highlight the Employee table, and under "Set Privileges, Edit" change
>>to "Limited". You'll then be able to enter a validation calculation,
>>like "Status <> "InActive". This will protect the entire record from
>>modification once it's set to inactive, without restricting creating or
>>deleting records.
>>
>>On May 18, 2005, at 1:45 PM, Donnie Mayes wrote:
>>
>>>Greetings;
>>>
>>>I have a field that marks an employee either Active or Inactive.  Once
>>>Inactive, I have locked them out of changing the Hire/Exit date with
>>>this Validation calculation:  EXIT DATE = STATUS <> "InActive".  They
>>>can not override this error message.
>>>
>>>We don't want them changing back the Status back to Active so they're
>>>able to change the date either, but when I try that calculation, once
>>>I change it to Inactive, it won't let me do anything.  I can't create
>>>a new record, do any finds, or anything on it.
>>>
>>>It is stuck there in limbo.  Is there a work around for this?
>>>
>>>We also have in big red letters, Inactive Employee Record come up when
>>>they change it to Inactive.  I think I remember seeing some newsletter
>>>where you could make text blink, but I can't find where it was.
>>>
>>>Any suggestions would be greatly appreciated.
>>>
>>>Thank you.
>>>
>>>Don Mayes
>>>
>>
>>Jim Main
>>-------------------------------------------
>>619-948-5293
>>[hidden email]
>>-------------------------------------------
>>
>>
>>------------------------------
>>
>>Message-Id: <[hidden email]>
>>From: Jim Main <[hidden email]>
>>Subject: Re: Globals in FM7
>>Date: Wed, 18 May 2005 17:24:32 -0700
>>
>>It appears the pre FMP7 trick of entering 'Define Fields' no longer
>>sets the server globals to the client's values. However, if you want to
>>blank out global fields that have values on server, you can from a
>>client switch them to non-global, then back to global fields, wiping
>>them out.
>>
>>I personally use an openning script that initially sets all global
>>values I want throughout the system from nonglobal fields into idental
>>global fields. Then I don't need to worry about relationships between
>>each TO and the global fields.
>>
>>On May 18, 2005, at 10:27 AM, Derrick Fogle wrote:
>>
>>>Is there any way to really change the value of a global on the server
>>>in FMS7A so that it 'sticks' and starts showing up in all the other
>>>clients?
>>>
>>>Derrick Fogle
>>>[hidden email]
>>>
>>
>>Jim Main
>>-------------------------------------------
>>619-948-5293
>>[hidden email]
>>-------------------------------------------
>>
>>
>>------------------------------
>>
>>End of  Digest #830
>>*******************
>>
>
>
>--
>------------------------------
>This list is a free service of OmniPilot Software, Inc.
>http://www.omnipilot.com/
>Search the list archives:  http://www.listsearch.com/filemakerprotalk.lasso
>Manage your subscription:
>http://www.listsearch.com/filemakerprotalk.lasso?manage


--
------------------------------
This list is a free service of OmniPilot Software, Inc.  
http://www.omnipilot.com/
Search the list archives:  
http://www.listsearch.com/filemakerprotalk.lasso
Manage your subscription:  
http://www.listsearch.com/filemakerprotalk.lasso?manage
Loading...