AccessHosting folks finally gave me an account. I published a test database into it after running the compatibility check with no issues.
In the web it does not work and I kept getting the message below.
Report viewer failed to set the report parameter defaults for this report. Select new default parameter values from the tool pane. An error occurred during local report processing. An attempt was made to set a report parameter 'SMID' that is not defined in this report.
I totally do not understand the message and appreciate if you or others can provide some in sight to overcome it.
The flow is as below.
When the program launch, a form is displayed by Salesman.
When you click the View Report button a report should open and be filtered to the selected SMID.
For items 5, the capacity of 500K rows in a table seems like a limiting factor to adopt this exciting web feature. Some trading houses I worked with have normalized data of approximately 1 million rows (4 years records). Many use 1+3 years sales data to
forecast future performance. A query is only as good as what is in the table we are quering into. How to overcome this?
My sincere apologies, if some of the questions are intimidating or seeking answers that are obvious.
Can I publish to Access Services an accde format (I do not want any design changes by other users)? When any users login or run their FE when connected to the web will they get all new design changes for both web and client objects while online? Most of
the text I gathered from the net does not specifically address accde online update.
Access 2010 has both Web objects and Client objects (Form, Report, Query etc.). If I am not interested to run in browser, should I just create with Client objects and still get all the benefits of the web link (multiuser like environment). The reason
why I want to create with Client Objects is because I can use VBA + Macros.
Are there number of users’ limitation? How many users can run their FE (accde) simultaneously to enter new data or retrieving it online?
Are there any rows (in table) limitation, 1 million, 10 million or more rows of records.
When I create a new Web database and decided not to Publish it to Access Services, can I still create the conventional split to FE/BE and expect it to function normally (even if I had created all my objects with Web objects)?
Is it difficult to create user level security in Sharepoint 2010/Access Services. The usual expectation is to limit a subset of data only to certain users. If I am not wrong, Access 2010 will cache all data into the local table once a user gets online and
all is dangerous.
Can multiple column primary keys be set? I use this in a number of my tables to prevent duplicate records.
In my database, it is not uncommon to run bulk delete and append queries to a data table. Can an administrator still perform this function in web solutions?