Changing or Adding a New table in a db design

[Lou_Reed]

Is it acceptable to change or create a new table once a database design has gone far along? I just have some question about one db table and I think the only way to answer


is to create another table using the same parameters and see what happens.

I am just reluctant to do this because tables are the foundation of the whole db. Again you are messing with the foundation of your building hoping it does not come
crashing down.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[jwhite]

In best-world scenario we always get the schema correct before we start building the UI; sometimes we don't. So, sure, it is acceptable to do so afterwards because, well, you have to get it right.

[Lou_Reed]

My second and third questions are as follows: what is the difference (if any) between building a query in the Navigation pane and using its name as record source and just putting the query's SQL code in the form's record source?

It seems that they are very similar.

Also is okay for a form to not even have a record source? Please understand these question just apply to code that I that was written by my predecessor not me. Hence the questions.

Any help appreciated. Thanks in advance.


Respectfully,

Lou Reed

[jwhite]

If you put the SQL in the RecordSource, then only that object will be able to use the statement; if you store the query by name and reference the query name as the RecordSource, then you can use the same query on multiple objects. On another note, using a query (either direct or stored) is preferred over putting a table name only which will return all fields - if not all fields are needed, then use a query.


It is possible for a form not to have a recordsource, but is not common. All depends on the logic and/or business requirements.