[note to self] to-do list para la base de datos del cdl

[cut]. bugs

  • program shuts down when shifting across entries too quickly in the multiple related tables form mode. really annoying! other interns and T think the db is «cracked» because of this bug. they started again relying on MS word and excel.. orz

one solution: reduce number of related tables and merge them?
second: related to one, merge cdl.data and cdl.general into one file?

2. funciones que necesitan ser agregadas

  • parameters with queries, since there can’t possibly be a query per variable field. estuve a punto de entender eso el otro día (es decir, hace tres meses) con el access help, así que hay que seguir probando.

===> done

  • need to add a whole new field for the placement exams as required by the department of education. they liked the way we organize data (apparently?) but frowned at the lack of placement exam records. T is getting some pressure from them, I think, so we need to work on that. I will get an excel chart done on that, as this requires some prioritization, but in the long run it needs to be incorporated in the db.

3. maintenance task that needs to be finished.

  • finish up polishing variable names so that they don’t overlap as soon as possible. as several field names were replaced over the last months, previous cumulative query structures became obsolete T.T which proved fatal at the recent workshop phone-a-call
  • create accessibility form pages for all functions of the db (currently only available at the «add students» «edit classes» and «add cases» level.) we need: just as starters

4. structural issues found

  • T will never use the database! orz
  • our clients have highly unstable information, their phone numbers & home addresses become obsolete within months. should so much effort be put in maintaining a comprehensive system backtracking client history info? maybe this just needs to be made simpler more apt for statistical analysis, à la excel.
  • i have a hard time remembering the 100 headstrong variable names. not to say of «query-specific variables», which don’t even show up at relationship diagrams. i print relationship tables often but it’s getting off limits soon. i need a second monitor, and win2k won’t support dual monitor for s3 savage ix/mv, while wn98 and winxp will do. ugh. i need to upgrade to xp at the soonest possible.[/cut]

Publicado

en

, ,

por

Etiquetas:

Comentarios

Deja una respuesta

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *