Hi Andrew, ----- Original Message ----- From: "Andrew Jensen" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, April 02, 2007 3:03 PM Subject: Re: [dba-users] Data Base error correction
> Hi Ron, > > Are you asking how to correct an error in data input or are you asking > how to correct an error in defining a column in a table. > > In the first case, an error in data entry, you can use a standard SQL > UPDATE command. > > However, I think you mean the later. If you need to change the data > type of an existing field and the table editor is not allowing it, it > may be because the database engine is not allowing it. In any case it > should be offering to drop the column and add it at the end of the > table for you. If you have data in it, you most likely keep answering > no to that. > > In the case of an embedded Base database you could try issuing an > ALTER TABLE command directly in SQL command window. Failing this > working then you will need to > > a) Copy your table to a new one. > b) drop the column in the original table then add it back with > appropriate changes > c) transfer the data from the column in the 'Copy' back to the new > column in 'Original' > d) delete the copy of the table > > Andrew 'Drew' Jensen > > On 4/2/07, Ron Horsley <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Can someone please advise how I can correct an error in a field in a db. > > I keep getting stuck in Design View that does not allow editing of fields > > but this facility is essential for updating records and error correcting and > > the help pages give me no alternatives. > > Thanks, advice will be appreciated. > > Ron. H > > Warwickshire > > England > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ===================================================== Thank you very much for your reply, I have yet to try your suggestions but feel I did not make myself very clear in my first mailing so will try to explain. Firstly the 'errors' I refer to are mine that crept in when I had to create a new database in MS Excel spreadsheet format for the purpose of loading and creating a database in OOo. I am looking for an alternative to Lotus Approach which is a database in their own language. Looks and works like a spreadsheet and does a lot more beside which is important. I am using it for a membership database with around 36 columns and over 50 lines. Each member's details is in a line. I need to access records quite frequently, weekly and monthly at least to change anything and everything:, e.g.; phone numbers; e-mail addresses, delete members; add new members; change addresses; change subscription details which occupy 4 columns and to get outputs. My access is required to remove existing or make up completely new lines but mostly it involves altering the content of 1 to 4 Fields only, and to get different outputs. 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. Unfortunately, and the reason for me looking to use OOo is that very few people have Lotus SW and I have to duplicate my efforts and find work-a-rounds whenever output is required for MS Word documents or sending in e-mail messages. Spreadsheets on their own involved a lot of extra work keeping them in parallel and up to date or copying and pasting to produce extracts. This is when errors creep in. That is why I moved to Approach. I have very little knowledge of SQL, or equal, working and do not know how to proceed in this case. With Approach it is not necessary. I imagine that MS Access would do all that I want with ease but at a price that for me to finance personally is not-on. If I can get OOo working in the way I need, like Approach, it will obviously be of interest to others. It may already do it all but I struggle to find out how, hence my requests for help when the Help pages get me lost! Am I asking too much from OOo at this stage in its development? Sorry about the length of this reply and I am most grateful for the help I receive and will work on this till I know for certain that OOo will do with speed and ease what Approach does for me and probably Access would do or just have to admit defeat! Regards Ron. H Warwickshire England --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
