Search results

This one goes back decades, but I had occasion to use it recently and it still worked.

The video is now available on YouTube.

In your original post: "How do we historicize all documents dated before 2025 in the DOCUMENTS table and then physically move them to another database," One or the other is true. Either you do want to "physically move them" or you don't.

Over the years, a number of discussions here have included methods of implementing unique, sequential numbering. https://www.access-programmers.co.uk/forums/search/6036910/?q=unique+sequential+number&t=post&o=relevance

An append query, followed by a delete query, both with appropriate parameters, would do the job. You can retain access to the archived data by linking it to the production database. I am not sure, though, what you mean by "historicize" them. How is that different from moving them to the...

100 fields? Let's step aside from the discussion of layout and ask what kind of process involves up 100 separate fields? If that represents fields in a single table, it throws a red flag up. If it represents fields from different tables, it throws a different red flag. If it represents fields...

:unsure: 😉 (y) And hence my question.

Probably, but in the real world "Startup"<>"Default". Sorry, but ambiguity always sets my teeth on edge. Maybe today is just the right day to let it out.

What do you mean by "default form"?

How about a supporting screenshot showing us the tables involved and the fields involved.

RIP Jack. A true Gentleman and wise friend.

GP George: That link doesn't work for me - HTTP 404.0 not found. Wow. I don't know how that folder got deleted. Thanks for the heads up. I'm rebuilding it now, but it will take a few minutes

I give up. Best of luck in the venture.

I have a sample database which illustrates the concept Duane described. https://www.gpcdata.com/Downloads/MainFormFilterSubform.ZIP

As I've stated ad naseum. SSMS -- SQL Server MANAGEMENT Studio -- is used by developers and DBAs to Create, alter and delete databases in SQL Server instances or in SQL Azure Create, alter and delete tables in databases in SQL Server Create, alter and delete views in databases in SQL Server...

Much clearer and more precise than my long-winded offerings. Thank you.

No, I do not envision someone who purchases a license to use an Access/SQL Azure database application needing to be a DBA to use it. That is precisely the point of purchasing a licensed product from you. They do not need, or want, to be a DBA and trouble-shooter. They are paying you for that as...

SSMS is required ONLY for YOU, the developer, who creates and manages the databases, and for any DBAs maintaining the SQL Server database on behalf of the user. SSMS is NOT required by users who will license your Access application for their use. In fact, you should hope that your end users do...

Two things leap out at me. "I am trying to make it as difficult as possible to use my Access FE at a reasonable price." I think that is a typo or misstatment, is it not? Do you REALLY want to make using your application difficult? "...running SSMS locally using SQL Server 25." No, your...

Ha. Garbage in, Garbage out. Asking AI to rank HI is bound to be ridiculous.