Search results

  1. BlueSpruce

    Access vs Comercially available databases

    That's why Windows Authentication with no service accounts is the preferred method for connecting to SQL Server, Oracle, PostgreSQL, and other db servers. If you can't pinpoint the culprit, then you have to detain all users and hang them upside down by their toe nails until someone confesses.
  2. BlueSpruce

    Access vs Comercially available databases

    You can grant them DBA privileges and the db will still be safe because none of the authorized users would know how to, or would dare mess around with something they're not supposed to touch. The db audit log would reveal who did what, when, and they would lose their jobs and face criminal charges.
  3. BlueSpruce

    Solved Unkown Cls/Collection Holding An Event

    Well, container types are not really applicable to what you're looking for since container collection and container objects are part of the DAO object model. The names Microsoft chose for container collection and container objects is ambiguous, confusing, and poorly documented. Nothing new with...
  4. BlueSpruce

    Solved Unkown Cls/Collection Holding An Event

    Have you tried using the object browser? You can also query the Name field in the MsysObjects table for Types 1 and 3 objects: SELECT vTbl.ObjectType, Count(vTbl.ID) AS CountOfID FROM (SELECT Switch(Type=-32768,"Forms" ,Type=-32766,"Macros"...
  5. BlueSpruce

    Clear out data

    @DakotaRidge's rationale is to provide his users with hardwired forms, customized for a single specific purpose, e.g. a form for food bought at Wamart, another form for recalled food, another form for recalled medications, and so on. He doesn't want a generic form for all cases, all vendors, all...
  6. BlueSpruce

    Access vs Comercially available databases

    ... and that's why SQL Server role based permissions can be setup for Active Directory groups. Even the healthcare applications I work with at major hospitals, which are HIPAA regulated, use Windows Authentication.
  7. BlueSpruce

    Access vs Comercially available databases

    That implies a person who already has Windows login credentials, and enough knowledge to set that up. I have yet to hear about a case where someone who is authorized to login to a workstation has perpetrated a SQL Server hack using that method. If you can't trust your own users, then what's the...
  8. BlueSpruce

    Access vs Comercially available databases

    Please explain how exactly that's possible. There are many enterprises that use Windows Authentication for SQL Server connections. If what you say is true, no one would use that method.
  9. BlueSpruce

    Access vs Comercially available databases

    Why not use Windows Authentication, which leverages existing Active Directory credentials? That eliminates the need to manage separate logins and passwords for SQL Server.
  10. BlueSpruce

    Access vs Comercially available databases

    Agreed, I did mention that towards the end of this post. If I were the OP, I would defend the current Access app for all the merits mentioned in this thread.
  11. BlueSpruce

    Access vs Comercially available databases

    I've already cashed in on several settlements. Makes me want to put more of my personal info out there so I can have another source of steady income 🙂
  12. BlueSpruce

    Access vs Comercially available databases

    An online app is automatically less secure than an on premise app. Then you also have to worry about the outfit that's hosting your data. No thanks.
  13. BlueSpruce

    Access vs Comercially available databases

    You're being cynical. If you feel Access is so insecure, then why do you develop with it, or even use it?
  14. BlueSpruce

    Access vs Comercially available databases

    Hey All, it would take an experienced Access developer to do all those hacks you mentioned. How many of those do you have at your company? Your average Access user is not going to know that. If you can't trust your own workers, then how can you operate? and I said "sufficiently secure", not...
  15. BlueSpruce

    Access vs Comercially available databases

    I disagree. If setup correctly, an Access application can be sufficiently secure. The setup your company uses is not correct.
  16. BlueSpruce

    Access vs Comercially available databases

    Although what you mention is true, a hacker would need to login as one of the users in the AD group that has permission to access the directory where the backend lives. If SQL Server is used, then there's an additional layer of security.
  17. BlueSpruce

    Access vs Comercially available databases

    The native Access backend can be secured with Active Directory. The frontends with Windows Authentication. If additional security is wanted for the data, use SQL Server. I also prefer having the data on premise versus in the cloud, hosted by third parties.
  18. BlueSpruce

    Access vs Comercially available databases

    So document your Access app well, including technical and end user documentation, and bring another Access developer, or firm, on board. Explain to management the pros of your Access app, and the cons of COTS software. You can also integrate instruments with your Access app.
  19. BlueSpruce

    Clear out data

    Well, I know he still receives emails of our posts. He'll be back... How many other Access apps with similar design do you think exist?.. Millions! I've come across several, all built with macros, tons of tables, queries, forms, reports. Why do they build apps like that?... They're using...
  20. BlueSpruce

    Clear out data

    I'm pretty sure he has repeated fields scattered across several tables, and specific fields, like WalmartItemName, MedicationName1, Name2, etc.
Back
Top Bottom