Bill,


I always had issues using the archiving function on 6.3, maybe others had
better luck, but I stayed away from it. Now in 7. it did work and worked
very well.



Just an example in 6.3 I tried to use it for the e-mail messages form. There
appeared to be a record limit on the receiving form as well as one on the
main one. Needless to say with the help of support we re-imported the mail
messages form and used a little workflow to save off data.

On Fri, Dec 19, 2008 at 11:48 AM, William Rentfrow <
[email protected]> wrote:

> ** I am working on an old server on and off doing some archiving for a
> customer.  I'm so used to 7 now I can't remember all the differences between
> 6.3 and 7 when it comes to archive forms - and I haven't worked with
> modifying them all that much anyway...
>
> Case in point - we've archived the main issue form from CSS (SPRT:Issue)
> and the system created a backup of the form.  Consequently one of the tables
> that shows child records is broken because the ID field needs to be
> re-directed to the archive form "Original Issue ID" - not a bid deal
> there...
>
> However....when I try to edit the table field and open the properties to
> the "table properties" tab I just get a blank "Not applicable" tab.  This
> also happens if I copy the control and try to create a new one.
>
> Was this a limitation in the 6.3 app?  You can't change anything on the
> form?  Or is there a way around this?
>
>
> William Rentfrow
>
> Principal Consultant, StrataCom Inc.
>
> [email protected]
>
> 701-306-6157 C
>
> 952-432-0227 O
>
> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___




-- 
Howard Richter
Red Hat Certified Technician
CompTIA Linux+ Certified
ITIL Foundation Certified
E-Mail = [email protected]
LinkedIn Profile = http://www.linkedin.com/in/hbr4270

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to