Recent content by CJ_London

One correction from me - you migrate access back end (tables and possibly queries from front end) to sql server, not access and not SSMS. SSMS is just the tool for managing sql server in the same way you would use access to manage access tables (and queries). You cannot use SSMS to create forms...

depends on what the app is doing. DAO is probably easier since the form sort/filter actions will work out of the box. But it is potentially less secure if you don't tie down who can see what in terms of the back view - tables, queries etc (i.e. hide that access navigation window). You should...

Decide first whether you are going to connect to sql server using DAO or ADO (although you can do both if relevant). DAO typically means you will be using linked tables, ADO means you will be creating recordsets as required and assigning them to form/combo/listbox recordsets. Performance wise...

Doesn't answer your question, but I've used AI to map a project - how forms/queries/reports/modules etc relate to each other. Simplistically generating a flow chart. As you say download using saveastext (or save as unicode8) then inspect all forms for subforms, all code for calls to open a form...

in this scenario what's the difference between handling a a multi column index where a clash arises and a unique key as you describe?

not clear on the requirement - if a user moves say the bottom record to the top - do you want just that record moved? i.e. break the grouping. Or both records (GroupID=3) to preserve the grouping? If the latter, you will need a second sequence column to sort on, rather than groupID

The danger with that is users look at the code and not the real differentiator (such as full name and address) - and can then select the wrong record and not notice

Personally I would keep your PK as an autonumber and store the other data in other fields - just concatenate them together when required for presentation purposes Simpler and safer

why? surely you would be deploying sql server? Not to say the client couldn't install SSMS themselves

OP really needs to create a security strategy document - protecting what, from whom, from doing what and how they could do it, backed up by a risk assessment. Once that is done, put relevant procedures in place. Some risks will be so low, it does not justify the cost of implementing the...

That was my point 😀

Therein lies your problem - trying to sell a model T ford in today’s market. If your app is fully inward looking and does not integrate with other apps (such as outlook or web technologies) then the code should continue to work regardless of other changes - at least for 20 years or so. I...

Which is why, if your product is so valuable you should be looking at a web solution. An alternative is to use terminal server - which has a licensing cost, can use your access FE and can be accessed by any device that supports TS. You control access to the server and can apply patches/updates...

You’ve been a member for 8 years and asked the same question 2 years ago https://www.access-programmers.co.uk/forums/threads/record-date-time-entered-user-login.326326/

Lost track of your chosen pathway - but if your client has an IT dept ( who will have their own patch strategy) or just has a policy in conflict with yours, think you will struggle with that approach Not quite the same thing but I have clients who use outlook automation and I’m constantly...