This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My organization is using MS Word form to create a client questionnaire. Each Word doc form is saved as PDF file and stored in the Client's folder. I created a form in Access to capture and parse the questions but I cannot find a way to create and output a PDF file from Access. This requires me to repeat the entry process manually into the Word document. My IT department won't let me roll this out to other employees because of A) the double entry issue and B) they fear other users apparently will have to learn and use VBA to output individual records.
My question is: Can Access output individual records as a printable PDF format and cannot it be done without VBA?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I can answer the one question... You can set two Primary Keys by highlighting both rows and then pressing Primary Key.
David,
Me <--no degree in Computer Science.
I did have a great teacher who was a co-worker. I learned a lot for her but more from the great help I received in newsgroups as there were no forums at the time. If I were a beginner now I would start with Crystal's book which is free...
http://allenbrowne.com/casu-22.html
You can also go here for free Data models...
http://www.databaseanswers.org/data_models/
https://www.access-diva.com/tips.html#bmDataModels
Access is simple enough for non-technical Users but once you start getting *serious* you do need to do some reading. And those hundreds of hours are over time with the help of the many Forums where free help is given including helping you create a data model. So if you ever decide it's worth the time, we are here to help.
I also noticed you said you created a Form and tried to add fields from another table which sounded like it was unrelated to the record source of the Form. Well, this can only be done when table is part of the record source. You can create a query which can include multiple tables from which you need fields and build your form though most would just use a subform in a typical one-to-many scenario.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 51%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I also recently learned that Access isn't really built for multiple users. I read that ten users are ideal. I work for a small business with nearly 200 employees so, it looks like Access won't deliver.
Where did you learn this false information? Access, by default, is set as a multi-user database. two hundred users is well within parameters. I've written databases that have been used by more than 100 users simultaneously.
You keep making false claims about what Access can or cannot do.
As far as your ability to work with service items. As Gail said, you should have a separate table for service items because you have a 1:many relationship. As for entering the ClientID automatically, this is a built-in feature and one of Access's most powerful Its called an embedded subform. If you create a main form bound to the Clients table and a subform bound to the service items table linked on clientID then any service item you enter into the subform will automatically populate the ClientID.
In all fairness, Scott, a well designed, professionally built Access Relational Database application can support many, many users--100 or more in ideal cases such as those you created.
When someone reports that they haven't been able to support more than a handful of people, it probably reflects more on the developer's limitations than the tool.
Hmm and let me just add to what Scott said...
If the database was prone to crashing and corruption then I would look to the design of the database. I have databases with 100's of Users that have been up and running since Access 97 (obviously upgraded over time) with no issues. And while I prefer to put the Backend on an SQL Server Access itself can handle it. I would not blame the saw because the cut wood is crooked.
That said, Access, unlike Excel, has a learning curve the most important being normalization and the close second is building a proper data model. If those older databases were built without knowledge of at least those two items they are going to have issues but not Access' fault.