Recent content by tvanstiphout

> or accessing the stored procedures and functions Look up "WITH ENCRYPTION" clause in BOL.

> you should be able to install an instance of a SQL Server with an SA account for which you have the credentials for Ha! There is the little-known gem that users with full control of the server {e.g. Domain Administrators) can always take control. See for example how to reset SQL Server sa...

Help files are mostly online nowadays. Search online for "VBA StrConv" and you should find the page you are looking for.

That is called vbProperCase. You can use the StrConv function for that. Look it up in the Help file.

This is what we implemented in Northwind Dev Edition, OrderDetails form. Works well.

A timestamp / rowversion column is an 8-byte array. You can write code to convert it to something humanly readable, but mostly it works behind the scenes. The value gets updated automatically by SQL Server when the data in the row changes. It can then be used for a concurrency check.

Did y'all miss this part of the OP's post Here actual table Name Employees <<<<< GrandFather --------Enrollment <<<<Father --------------------CafeteriaData <<<<Son This can be solved with normal one to many relations. tblEmployees EmployeeID autonumber pk EmployeeFirstName text20 required...

Check out Application.ImportXML, ExportXML and TransformXML in the help file.

Thanks for this, but it does not QUITE get to the core of my question: can one task have many specs, or can each spec be part of many tasks, or both. That would make it a 1:M, M:1, or M:M relationship.

I looked at your db and it does not make sense to me. Starting with the relationships: This means that each Spec is made up of many Tasks. However, when I read the Spec records, these seem to be very minute instructions to fix something about an engine. That would mean: Task = Fix engine. Specs...

"Type" is a Reserved Word and it should not be used for a field name or any other object name. Search online for "Access reserved words" to get the full list.

2501 is not really an error. That's why in the Northwind 2 Developer Edition template's central error handler we write: If lngError = 2501 Then Exit Sub '2501 = The OpenForm or OpenReport action was canceled. Not really an error.

That would require the db to be queried twice - unnecessary in light of the Report_NoData event.

Here is a quick and dirty example. Compile testLib to .accde. Open testApp, and fix up the reference to that library. Run _modTestOnly.test1Form

Re the demise of Access: https://www.accessforever.org/post/how-to-counter-rumours-of-access-demise