Hi Andrew and Alex, Thank you very much for your messages and help. May I continue this, I repeat most of the previous messages with my 'Response'.
----- Original Message ----- From: "Andrew Jensen" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, April 03, 2007 11:15 PM Subject: Re: [dba-users] Data Base error correction > Hello all, > > Alex - I am sorry but I really must disagree with your comments. I > think Ron's needs are fully met within OpenOffice as it stands today - > and I would not be surprised if he never once has to see an SQL > command. As for any macro programming - maybe some ( 2 or three line > scripts), but then only if he wants to. > > Ron - reading your second message with the description of your Lotus > Approach database I am in a somewhat better position to comment - > thanks. > > Agree with Alex the data entry/edit tasks will be simply met, your > output - all though I need to hear more specifics - will most likely > be easily met also. Most likely as a simple report. 'Response' ... I have felt all along that OpenOffice will do what I want and probably more and be easier to use being communication friendly with MS products. If I can only get around finding my way about the OOo package (V 2.1 from a CD bought locally at a resonable price from a company in the Midlands who are listed on the OOo Website). >>>>>>>> (((Several lines cut from long messages to save space))) > >> The outputs used are in 9 types; 6 in different mini-spreadsheet layouts > >> from 3 to 15 different columns and all the 50+ lines; 1 form that includes > >> all the individual's details, i.e.,. every field in a line for 1 member at > >> a time; 1 that is for addressing envelopes; and 1 that will print a 3x7 > >> label A4 sheet of address labels. >>> > >> With Lotus Approach if any single field or line is changed on the main > >> worksheet or any of the 'outputs' the identical field is changed at the > >> same time automatically on every other one of the 9 outputs without > >> requiring any additional action from me. I need this from OOo. > > >This is doable, but not easily by someone who knows nothing about programming > >or database languages. > > Alright difference in terms here. The Lotus Approach workseet is the > same as a table in Base. The outputs, all though I can't be certain, I > am willing to wager are equivalent to Base queries or forms. 'Response' Yes they are; Worksheet=Base (containing every line, column and field to which all 'outputs' are linked), it looks just like an Excel Spreadsheet/Lotus-123/OOo Calc but I assume has special properties; Forms in Approach can be produced in different layouts but the Standard I use is just like an OOo Writer page with Mail Mergs links to columns/fields displayed as one wishes. Nothing complicated. >The mini-spreadsheet layouts are just queries or forms in Base. 'Response' Yes exactly, selected columns extracted from the Base/Worksheet for printing. In Word format they could be attached to other documents. >In either > case, yes editing the data in any of the later will reflect the change > to all different 'views' of the data, because the data is stored in > just one table. ( functionally identical to what Approach is doing ) 'Response' Excellent just what I want provided I can have several 'Views' and be able to print them etc. > > The envelope addressing and label generation are handles using Writer > using your Base data as the datasource. 'Response' Yes I can do envelopes OK, have not tried labels. > > You say you need to export Excel spreadsheets for other, well here is > where OO.o will shine for you - linking your Base data to spreadsheets > is very simple and this link can be setup so that you will refresh the > data automatically every time the spreadsheet is opened. Calc then > offers you the option to save the file in Excel format. 'Response' Again excellent. > > About the problems you are having at the moment, I can only hazard a > guess. You said that you exported your data from Approach into an > Excel spreadsheet and that you are opening this using Base - now you > can do that of course, but then this is a read-only view of the data. > What you really want to do is import that data from the Excel file > into a native Base database. > > OK, that all sounds good right - but leaves you no better off for reading it. 'Response' Agreed. What I have is 'read only' what I would like is the ability to Edit any and all Fields. The drop-down menu for Edit is feint i.e,. not available. I wonder if this is my fault, did I tick the wrong box or something when producing the Base from a spreadsheet? What is the difference between Base and a native Base database. > > A little while back, on this list, there was a discussion about > example databases. Along with this discussion there has been a fair > amount of activity regarding creation of tutorials. Well Ron, truth is > I think your Approach application is about as close to the simple > 'Real World' example database that was talked about in the earlier > discussion as can be found, also a tutorial ( case study) on migrating > an existing Lotus Approach application to OpenOffice sounds like a > real winner to me. > > So - I will make what I think is a win - win proposal to you. I ( and > anyone else that wants to lend a hand ) would help you convert your > club membership database from Approach to OpenOffice. We would keep a > running commentary on the work needed to do so - It would be very > interesting to have your take on the differences between the packages, > as you go, as part of that commentary. ( exactly where we would do > that I'm not sure, maybe the wiki, maybe not - but we could work that > out easily enough) 'Response' A marvellous offer and I am most grateful for it but I did find 'a simple man's' way of doing it. I had a MS Excel spreadsheet with about half of the columns on it so only had to add the other columns. This was part produced earlier by scanning a print of the Worksheet running it through an OCR programme and dropping it into Excel. Because I was also revising the information and cutting out a number of colums that are not essential it was not a difficult job. This is where I made 2 or 3 errors and then found I could not edit them, start of story! > > > When we are done, the database ( sans any real persons identifying > information of course ) would be placed into the public domain as an > example database, along with the associated Calc and Writer templates > / documents needed. Then, with a little luck we might find one of the > good folks at the OOoAuthors group to help polish the running > commentary and turn it into either a tutorial or a case study. > > Time wise, this will not take a great deal - a good weekend or two of > time should do the trick. > > So what do you say? 'Response' It would be very interesting as an exercise but a long learning curve so I regret I must decline the idea due to other commitments that have to take my time for sometime ahead. > > Sincerely, > > Drew Jensen > > Your have brains in your head. > You have feet in your shoes. > You can steer yourself any way that you choose. > --- Dr Seuss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > 'Response' I think you have got the point exactly that OOo will do what I want, it is just getting the terminology right and putting it to work. Is there guidance available in downloadable printed (PDF) form that I could access and study to create a proper editable/working database/worksheet/Base, what ever it is called. Another correspondent raised 'Primary Key' which was new to me is this relevant to what has now been said above? Thank you again. Regards Ron. H Warwickshire England --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
