--------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5500002 Date: 05/03/95 From: JEFF KUZMA Time: 11:46pm \/To: GREG SMITH (Read 11 times) Subj: Pdox 5.0 GS>Hello from the home of the Lysander, Robert! GS>Greg descends through the clouds and hears Robert Pardoe say to Lance GS>Leonard:about Pdox 5.0 on Thursday February 16 1995 GS> RP> It's bearable, but I just hope someday Paradox and Windows work GS> RP> flawlessly with each other! Well, it's okay to dream! GS>I'm still waiting for it to work flawlessly under DOS, let alone GS>windows. That's a rather harsh statement, especially when you started out by extolling a rather mediocre aircraft! Maybe you ought to look at the concept from the other angle: both DOS and Windows leave something to be desired. === * OLX 2.1 TD * * ... File not found. Should I fake it (Y/N) ? --- TosScan 1.00 * Origin: Colossus - The Columbus Computer Society - Columbus, OH 1:226/120) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5500003 Date: 04/26/95 From: THOMAS WIEDMANN Time: 07:57pm \/To: BRADEN PINTAR (Read 10 times) Subj: Memo Fields * Braden Pintar schrieb an All am 21 Apr 95 21:46:00 * * Thema : Memo Fields * Hallo Braden, BP> I would like to know if it is possible to import a text file into a BP> Pdox memo field. I usually work in dBase, so I am a little at a loss BP> as to what I can get away with in this environment. Any help would be BP> appreciated. Thanks. if you had an Memofield like 'M', try this -------------------------------- methode pushbutton() M.action(EditPasteFromFile) endMethod -------------------------------- Tschues...Thomas ... Greetings from Germany, 71552 Backnang --- Blue Wave/Max v2.12 * Origin: Simple OS/2 BBS (2:246/1409) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5500004 Date: 05/02/95 From: MICHAEL KIMBALL Time: 09:28am \/To: PETER READER (Read 12 times) Subj: Adding procs to queries On 04-29-95 PETER READER wrote to ALL... PR> I just started writing a data entry application using Paradox 5.0 for PR> Windows because the place where I volunteer has standardized on that PR> custom or supplied (like IIF). Say I want a QBE field to contain PR> either the contents of table field A or table field B depending on the PR> contents of table field C. In Access I could write In Pdox3.5 I would set up a two line query. The first line would have field A checked and a condition in field C. The second line would check field B and have the different condition in field C. Thus: Field A Field B Field C "Something" "Something else" Of course I don't have Pdox running while I'm in my offline mail reader/editor, so I haven't actually tested this example. It might just come back with "DORK ERROR! DORK ERROR! Query appears to ask two unrelated questions". Also Pdox5.0 my be different anyway. PR> the function in a query column doesn't work, either, with or without a To my way of thinking this is definitely a failing of Paradox. One of the few, but a failing nevertheless. Another way might be to check all three fields and then run a PAL script on the Answer table: Edit "Answer" Home While Not AtLast() If [C] = "Something" then [A] = [B] [B] = "" Else [B] = "" ; and [A] keeps it's current value EndIf Down EndWhile Do_It! ... OFFLINE 1.50 "Speed Kills - Use Windows!" --- QScan/PCB v1.16b / 01-0057 * Origin: (1:229/140) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5B00000 Date: 04/30/95 From: FRANK MALCOLM Time: 09:29pm \/To: SOMEONE (Read 9 times) Subj: Sizing a form Somebody replied to my request about resizing a form to fit the displayed table in PdoxWin. Unfortunately an accident killed the mail packet before I could reply. Whoever, thanks for your comments. You mentioned setting the Size To Fit Property, and some other stuff - I think I tried that (I tried a heap of stuff :-() and from memory it was OK going from the design to the view data mode, but opening the form from scratch still left me with a big form with the table in one corner. Anyway, I solved the problem. Here's what I did... This method is in the form: method SetSize (TableW longint, TableH longint) var FormX, FormY, FormW, FormH longint endvar GetPosition (FormX, FormY, FormW, FormH) SetPosition (FormX, FormY, TableW + 170, TableH + 430) endmethod This method is in the table: method open(var eventInfo Event) var TableX, TableY, TableW, TableH longint endvar Self.GetPosition (TableX, TableY, TableW, TableH) Self.SetPosition (0, 0, TableW, TableH) #OpenOptsForm.SetSize (TableW, TableH) endmethod This seems to work OK. The funny numbers (170, 430) in the form SetSize method are to allow for the scroll bar and borders and were figured out by trial and error - once I realised the measurements weren't in pixels but in twips or something. Thanks for your input. Regards, FIM. * * Windows: an 80486 to XT Conversion Kit. --- * Origin: Pedants Inc. (3:711/934.24) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5B00002 Date: 05/05/95 From: JOE LABONTE Time: 03:45pm \/To: ALL (Read 8 times) Subj: IDPDX01.DLL SEGMENT FAILU I keep getting an IDPDX01.DLL segment failure when trying to use Paradox 5.0. What is this & how do I fix it? --- QScan/PCB v1.15b / 01-0348 * Origin: FidoNet: CRS Online, Toronto, Ontario (1:229/15) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5B00003 Date: 05/05/95 From: DAVID SHERMAN Time: 10:05am \/To: ALL (Read 8 times) Subj: Paradox runtime error Does anyone know the error message of GP0000 AT Pdoxwin:B4:00C4 mean? Thanks === * QMPro 1.53 * If Two Wrongs Don't Make A Right - Try Three! --- TosScan 1.00 * Origin: Colossus - The Columbus Computer Society - Columbus, OH 1:226/120) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5B00004 Date: 05/05/95 From: DAVID SHERMAN Time: 10:05am \/To: ALL (Read 8 times) Subj: Paradox 5.0 convertors Borland has release the Paradox 5.0 convertors. It is now on PIBB BBS at 916-686-4740. === * QMPro 1.53 * Is my room at Belview ready yet?????? --- TosScan 1.00 * Origin: Colossus - The Columbus Computer Society - Columbus, OH 1:226/120) --------------- FIDO MESSAGE AREA==> TOPIC: 119 PARADOX Ref: C5C00000 Date: 05/06/95 From: PETER READER Time: 09:44am \/To: MICHAEL KIMBALL (Read 8 times) Subj: Adding procs to queries -> In Pdox3.5 I would set up a two line query. The first line would -> field A checked and a condition in field C. The second line would ch -> field B and have the different condition in field C. Thus: I couldn't seem to make this work either in 3.5 or 5.0 -- I had hoped to use it in a query to base a canned report on that the user could select and run with a couple of mouse clicks. Guess I'll have to build an elaborate method to create and merge a couple of tables. Now to find out how to display an animated cartoon to keep the user occupied and bemused while all this goes on 8-). Thanks for trying to help . . . Pete peter.reader@nwcs.org --- WILDMAIL!/WC v4.12 * Origin: NWCS Online (1:105/362.0)