maximum records in form view

[Guest]

I have always used File Maker Pro because it is easy. However it does not
support Hebrew, so I have Hebrew Access. I have designed a simple, flat
database and made the form look just like what I used in FMP.

I have a date field, a subject field, a source field and a notes field. For
the notes field I set it to memo as I want the option to put long entries
there. I began making records and all was well. When I got to 186 records I
was able to create more; however, when I close the program and reopen, the
records after 186 do not appear.

Please provide help in simple, step by step instructions.

Thank you,

Jotwo

 

[Arvin Meyer [MVP]]

This is probably an error in your copy of Access. You can easily store
hundreds of thousands, and up to millions of records in Access. Even
considering that you are using a memo field, which can hold a lot of data,
you should be able to store 50 times that many records with each memo field
filled by data entry.

 

[Rick Brandt]

I have always used File Maker Pro because it is easy. However it does
not support Hebrew, so I have Hebrew Access. I have designed a
simple, flat database and made the form look just like what I used in
FMP.

I have a date field, a subject field, a source field and a notes
field. For the notes field I set it to memo as I want the option to
put long entries there. I began making records and all was well.
When I got to 186 records I was able to create more; however, when I
close the program and reopen, the records after 186 do not appear.

Please provide help in simple, step by step instructions.

If all of the records do exist in the table then your form is either bound to a
query that doesn't return all the rows or it has a filter applied.

Open the table and count the records. Open the form in design view and see if
the RecordSource is just the name of your table or if it is a SQL Statement. If
the latter press the build button to the right of the property box [...] to see
the statement in the query designer. Does the query have any criteria applied?
Does it include any other tables? Queries with more than one input table will
normally only return rows where there are matches in ALL of the tables so that
can limit the rows returned.

Switch to datasheet view of the query and see how many rows you get there. If
you get all expected rows then the form must have a filter aplied to it. On the
data tab you can see what is entered into the Filter property.

 

[Guest]

I have always used File Maker Pro because it is easy. However it does
not support Hebrew, so I have Hebrew Access. I have designed a
simple, flat database and made the form look just like what I used in
FMP.

I have a date field, a subject field, a source field and a notes
field. For the notes field I set it to memo as I want the option to
put long entries there. I began making records and all was well.
When I got to 186 records I was able to create more; however, when I
close the program and reopen, the records after 186 do not appear.

Please provide help in simple, step by step instructions.

If all of the records do exist in the table then your form is either bound to a
query that doesn't return all the rows or it has a filter applied.

Open the table and count the records. Open the form in design view and see if
the RecordSource is just the name of your table or if it is a SQL Statement. If
the latter press the build button to the right of the property box [...] to see
the statement in the query designer. Does the query have any criteria applied?
Does it include any other tables? Queries with more than one input table will
normally only return rows where there are matches in ALL of the tables so that
can limit the rows returned.

Switch to datasheet view of the query and see how many rows you get there. If
you get all expected rows then the form must have a filter aplied to it. On the
data tab you can see what is entered into the Filter property.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


Rick, thank you for your response. I have not designed a query. I have used control-f to find something. I do not know where to find the filter function. Pardon my ignorance.

There is the same number of rows in datasheet view as there are records in
form view. If I enter data either in datasheet view or in form view (beyond
the 186 records that are always there in both when I close then reopen) the
new records are simply no longer there when I reopen.

Jotwo

 

[BruceM]

Did you look at the table itself, as suggested? I am not very familiar with
Filemaker Pro, but from what I understand you build the structure directly
through the user interface rather than by constructing the database, then
building an interface for it, which is how Access works. Datasheet view and
Form view are different formats for the user interface; the data are stored
in tables that you can open from the database window (the box that shows up
when you first open Access). In order to use a form to store data the form
needs a Record Source (a table).

I have always used File Maker Pro because it is easy. However it does
not support Hebrew, so I have Hebrew Access. I have designed a
simple, flat database and made the form look just like what I used in
FMP.

I have a date field, a subject field, a source field and a notes
field. For the notes field I set it to memo as I want the option to
put long entries there. I began making records and all was well.
When I got to 186 records I was able to create more; however, when I
close the program and reopen, the records after 186 do not appear.

Please provide help in simple, step by step instructions.

If all of the records do exist in the table then your form is either
bound to a
query that doesn't return all the rows or it has a filter applied.

Open the table and count the records. Open the form in design view and
see if
the RecordSource is just the name of your table or if it is a SQL
Statement. If
the latter press the build button to the right of the property box [...]
to see
the statement in the query designer. Does the query have any criteria
applied?
Does it include any other tables? Queries with more than one input table
will
normally only return rows where there are matches in ALL of the tables so
that
can limit the rows returned.

Switch to datasheet view of the query and see how many rows you get
there. If
you get all expected rows then the form must have a filter aplied to it.
On the
data tab you can see what is entered into the Filter property.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


Rick, thank you for your response. I have not designed a query. I have
used control-f to find something. I do not know where to find the filter
function. Pardon my ignorance.

There is the same number of rows in datasheet view as there are records in
form view. If I enter data either in datasheet view or in form view
(beyond
the 186 records that are always there in both when I close then reopen)
the
new records are simply no longer there when I reopen.

Jotwo

 

[Guest]

Did you look at the table itself, as suggested? I am not very familiar with
Filemaker Pro, but from what I understand you build the structure directly
through the user interface rather than by constructing the database, then
building an interface for it, which is how Access works. Datasheet view and
Form view are different formats for the user interface; the data are stored
in tables that you can open from the database window (the box that shows up
when you first open Access). In order to use a form to store data the form
needs a Record Source (a table).

Jotwo wrote:
I have always used File Maker Pro because it is easy. However it does
not support Hebrew, so I have Hebrew Access. I have designed a
simple, flat database and made the form look just like what I used in
FMP.

I have a date field, a subject field, a source field and a notes
field. For the notes field I set it to memo as I want the option to
put long entries there. I began making records and all was well.
When I got to 186 records I was able to create more; however, when I
close the program and reopen, the records after 186 do not appear.

Please provide help in simple, step by step instructions.

If all of the records do exist in the table then your form is either
bound to a
query that doesn't return all the rows or it has a filter applied.

Open the table and count the records. Open the form in design view and
see if
the RecordSource is just the name of your table or if it is a SQL
Statement. If
the latter press the build button to the right of the property box [...]
to see
the statement in the query designer. Does the query have any criteria
applied?
Does it include any other tables? Queries with more than one input table
will
normally only return rows where there are matches in ALL of the tables so
that
can limit the rows returned.

Switch to datasheet view of the query and see how many rows you get
there. If
you get all expected rows then the form must have a filter aplied to it.
On the
data tab you can see what is entered into the Filter property.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


Rick, thank you for your response. I have not designed a query. I have
used control-f to find something. I do not know where to find the filter
function. Pardon my ignorance.

There is the same number of rows in datasheet view as there are records in
form view. If I enter data either in datasheet view or in form view
(beyond
the 186 records that are always there in both when I close then reopen)
the
new records are simply no longer there when I reopen.

Jotwo

Thank you, I will check this out

 

[Van T. Dinh]

Yes, your info regarding FileMaker Pro is correct. In FileMaker Pro, user
design the data structure and the GUI more or less as one object. Going
from FMP to Access or Access to FMP can be very confusing ...

Just a small addition for an Access Form that can be confusing also: a Form
can have different views (normal Form View, Continuous Form View, Datasheet
View and the worst one: a CtsFormView but designed to look exactly like a
DatasheetView).