Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Gracias por el desarrollo de su producto.
 Lo que me llamo la atencion es que en Base al generar tablas necesariamente 
hay que agregar un id para poder agregar o eliminar registros al crear la 
tabla. Si tuviera dos tablas con  casas con precios y otras con casas y 
compradores en access yo las pegaria y empezaria a realizar un cruce. Sin 
embargo, con esa limitacion de tener necesariamente un id, que en access es 
optativo, limita para aquellos que solo quieren analizar datos de volumenes 
grandes de datos sin ser experto. 
Otra no vincula archivo texto sino que se deben copiar. 
Su planilla de calculo es mas acabada y usable.
Word no lo uso en ambos asi que no opino.
Es mi pequena retroalimentacion
Jalexin

.....

Thank you for your product development.
 What caught my attention is that tables based on gender necessarily have to 
add an id to add or delete records. If you have two tables with houses and 
other houses prices and buyers access the fitting and I would begin to make a 
crossing. However, this limitation must necessarily have an id, that access is 
optional, limited to those who just want to analyze data from large volumes of 
data without being an expert.
Another text file is not binding but must be copied.
Your spreadsheet is more complete and usable.
Word do not use it in both so I do not think.
It's my little feedback
Jalexin

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.