Add field to the table in the backend

[Frank Situmorang]

Hello,

I have split my database into FE and BE. Since my specialty is in Finance
and Accounting, but with a selfthought I already created a supplier invoices
tracking database and already went live 1 year ago, but I did not anticipate
that number of recourds could be huge and users will be boring to scrolll up
and down in the datasheet view of searching the record.

So I plang to add the archived field in the BE database when every user
already quit their FE.

My question is can I do it and will not jeoperdize all the rules in the
database FE?, Can it be still developed in the front end to add archived and
later I will filter in the query not to show the archived?

What is the best way to excluded all the settled invoices from the users
record ( not be shown), I think we do not need to delete the record or
transfer to another table.

Thanks in advance for any idea provided.

 

[Albert D. Kallal]

I see no reason that would prevent you from simply opening up the back end,
and opening up the table in design mode and adding the new feel that you
need.

In fact I would assume over the lifetime of your application, that you're
often adding new updates, bug fixes, new reports, and on the ocation, also
add a few fields here and their too existing tables.

The process and things that you have to watch for after you add a new field
to the table is exactly the same with the non split application.

For example often people build a form using the wizard, and a query. You
often see people asking the question how come after I added a new field to a
table, it does not appear or can't be used in the form? The answer of course
that you have to go back and edit the query to add this additional field
into the query grid ...and *THEN* you'll be able to use that field on a new
form (I'm assuming you're distributing a new front end with the updates and
changes to the forums also).

of course if you're in a different location, or don't have physical access
to that back and tabled, then you're updating or modification of the table
structures is a little bit more tricky, and the solution that case is to
start writing some code to open up the back end database and add those
additional fields.

I will continue to watch this thread a bit, and if you're looking for some
sample code that does update the back end, just ask and I will post a few
lines of code (however, keep in mind that you really don't need this cut out
if you can just open up the back end table and modify the tables direclty).

 

[Klatuu]

Ditto on Albert's comments.
One question I did not see he addressed was limiting the form's recordset to
settled invoices.

I don't know the data type of the archived field you are adding, but I would
suggest it be a Yes/No (Boolean) data type. Then, if you are using the
table as the record source for your form, change to a query based on the
table and add the criteria to the query to filter on the archive field's
value.