Re: [PEDA] General component data tracking and library management questions

2003-01-27 Thread Wojciech Oborski
Brad, Ian, Sorry for jumping in so late, I've had busy days and read this thread just a while ago. The answer for the question: Why is it that we are finding these items now? could be - because they are well hidden :) Seriously, there is Protel's KB Item 1920 explaining briefly why Import

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Christopher Brand
And the dBase database linker: does it even work? Does it work *well*? Works to its limits and is very slow. It does not allow the footprint to be updated, for instance. Greetings All, I just wanted to chime in with my experiences using the dbase import function of protel. I agree

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Brad Velander
email: [EMAIL PROTECTED] http://www.norsat.com -Original Message- From: Christopher Brand [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 8:38 AM To: Protel EDA Forum Subject: Re: [PEDA] General component data tracking and library management questions Greetings All

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Ian Wilson
On 10:38 AM 23/01/2003 -0600, Christopher Brand said: And the dBase database linker: does it even work? Does it work *well*? Works to its limits and is very slow. It does not allow the footprint to be updated, for instance. Greetings All, I just wanted to chime in with my experiences

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Christopher Brand
Ian, The speed of the Sch:ImportSchematicFromDatabase is probably just as slow as the Sch:UpdatedPartDatabaseLinks. I remember playing with the database links a while back when we got protel98, but couldn't quite get it to do what I wanted. I don't remember how I found the

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Brad Velander
] General component data tracking and library management questions (Brad V - I noted your comment on this thread - No, Chris is doing a real import but from a dialog I had not seen or investigated before. Dunno the speed, maybe others that use database linking can benchmark

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Thomas
-Original Message- From: Brad Velander [mailto:[EMAIL PROTECTED]] Sent: Friday, 24 January 2003 09:57 To: 'Protel EDA Forum' Subject: Re: [PEDA] General component data tracking and library management questions -snip- Why is it that we are finding these items now! Four

Re: [PEDA] General component data tracking and library management questions

2003-01-23 Thread Brad Velander
email: [EMAIL PROTECTED] http://www.norsat.com -Original Message- From: Thomas [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 3:40 PM To: 'Protel EDA Forum' Subject: Re: [PEDA] General component data tracking and library management questions -snip- Why

Re: [PEDA] General component data tracking and library management questions

2003-01-22 Thread Brad Velander
Buck, I am sending you an email that I have shared with others asking some similar questions. Won't repost the same thing over again here. Sincerely, Brad Velander. Lead PCB Designer Norsat International Inc. Microwave Products Tel (604) 292-9089 (direct line) Fax (604) 292-9010

Re: [PEDA] General component data tracking and library management questions

2003-01-22 Thread Ian Wilson
On 03:18 PM 22/01/2003 -0800, Buck Buchanan said: Hi all, I have several questions oriented around the general theme of library organization and component data tracking (part #, distributor, price, etc.). I don't expect anyone to answer all of these, but opinions regarding any points here

Re: [PEDA] General component data tracking and library management questions

2003-01-22 Thread Ian Wilson
At 10:43 AM 23/01/2003 +1100, Ian Wilson wrote: Server can be found at http://www.considered.com.au/Protel01.html It was pointed out to me that I don't know my own site very well :-) There is no 'l' on the .html Correct link is: http://www.considered.com.au/Protel01.htm Ian * * * * * * * *