I'm going to be eliminating the associated lookup tables as I redesign my Q&A databases in Sesame.  In one database's case I'd like to incorporate the lookup table data into a "notes" field in the associated database.  Since I won't be importing the data until the redesign is done, and since the import can't "look at" the table, I'll need a way to key it into the imported records.  This would be fairly simple if there was a way to print the sucker out.  Any ideas?

Yeah, hmmm, I'm going to have to think about this.  Here's the thing: I've already translated the DTF to Sesame and am in the process of redesigning it, part of which is the elimination of the lookup table (incorporating it's contents into a "Notes" field).  Meanwhile, the DTF is still "Live" amongst my co-workers.  Until the redesign is complete I consider all the data I've brought over to be temporary, and plan to mass-delete and then import all the "live" data when Sesame is ready to go on line.  But there's no way to import data from a lookup table into the records.

I could redesign Q&A so that it has a mirror "Notes" field, but I still need a way to get the Lookup Table data into it.  The easiest thing to do will be to just key in the data in Sesame.  There's only about 80 records that need it, out of 24,000 records total, and each entry is only a sentence.  Seems like F2 works everywhere in Q&A except the Lookup Table.   

Hey, great, that'll work well!  Then I can do a Mass Update to lookup the entries in the new database and transplant them into the other, save me some keystrokes.  Thanks Erika!

Thanks Bob, sounds like just the trick.  I'm at Info@jamiara.com.

Quote:

It has not arrived.  Can you send it again, please?  If it's an executable file you might try changing the extension to something innocuous, like .txt.
Quote:

Nope, it's nowhere on my disk.

Thanks again, Bob!

Quote:

Hmmm.  Still not here, 4 PM.  "Both" addresses?  Not sure which ones you mean.  In any case:
Work:  Info@jamiara.com
Personal: Infinity@captaininfinity.us

The captaininfinity.us address has no filters in place, so it shouldn't be trapped, whatever it is.

Quote:

Yes, both the server and the workstation.

Quote:

No.  That would be a challenge.

Quote:

I have a Utils folder but not the rest.

Quote:


Ah ha!

There was a Q&A Bash?  Shoot, I missed it.  I really love Q&A.  I like the ability to whip up a report anytime I want with a few quick keystrokes.  Sesame is great, too, don't get me wrong, but its report module is a real headache.  I can't yet translate a vertical design interface into the horizontal thinking required for a report.  Can't wait for V2 to change that.  But another huge drawback is that it's in Designer, and requires a reconciliation in order to use on the live db.

Hey, when did the Forum get spell checking?  NEAT!  Now if only the Program Editor could do it!

Quote:

I have the Twilight Zone theme playing in my head, because I don't have an AOL address.
Doo dee doo doo, do de doo doo.....   AOL?  Is that thing still around?

Quote:

Ah HA!  So that's it.

Quote:

Got it, thank you.  That's the good news.  The bad news is that it doesn't work.  My database is in Q&A Version 5.   

Quote:

Okey Dokey, Smokey!

Anyhow, your email never appeared in my Info box and I don't see it in any of my ISP's spam or virus traps, so that's pretty weird.  But HOO BOY do a lot of strangers out there think I have erectile problems!

Thanks again, Bob!

Quote:

Not for me, sad to say.  The window closes and I get a zero-byte file named QA4LOOK.TMP.

We'll look at it next Saturday.  Thanks again for your help.

Sorry I couldn't make it to the user's group on Saturday; I had to work.

Anyhoo, when I click on QA4LOOK.EXE a command window opens, and the prompt appears.

Quote:


Yep.  I've put both the QA4LOOK.EXE program and the database (with both DTF and IDX files) into my C: root, and tell the prompt C:\INVOICE.DTF.

Quote:


Unfortunately, this doesn't happen for me.  Upon hitting "enter" the command window closes, and a zero-bit file called QA4LOOK.TMP is created.

So I started some experiments, thinking maybe it's a problem with my database.  First, I removed all security (it was a password protected file).  No luck.

Next I removed all records.  Nope.

I then created a single record, and performed a null mass update.  No luck.

Then I did a recovery.  Success!  I got the prompt asking for an output selection, choise standard ASCII, and successfully created QA4LOOK.ASC.   YAY!

Just for fun, I made another copy of my "live" DTF, performed a recovery only, and tried again.  Back to crashing.  Removed security.  Crash.  Did a null mass update (the DTF still contains 30,946 records at this point).  Crash.  Performed another recovery.  Crash.  So by now I'm really starting to think it hates my records.  So I started removing records.  I used year of creation as my criteria, first getting rid of 2006, then 2005, and so on.  After each "remove" operation I did a Recover to "pop the bubbles" left behind.

After removing about 4000 records, QA4LOOK still crashed, but the TMP file left behind had some size to it.  Looking at it in a text editor showed me numerous lines filled with just quote marks.   Hmmm.  Making some progress, not just need to fill the empty quotes with the lookup table entries.  Back to whittling away records....

Long story short, when I had reduced the file to 10,719 records (file size about 16 MB) QA4LOOK worked again.  SUPER!

So, what have we learned from this?  Well, mainly, that I have way too much free time on my hands.

Thanks for the program, Bob!