Search results

Well, currently I use Windows Task Scheduler to kick off some automation-oriented Access frontends that kick off some Make-Table queries that create tables in some backend mdb Access databases. The problem is that these backends can blow up to 2 GB pretty easily sometimes and cause issues with...

Could I, for instance, use automated Access frontends with SQL Server backends for the sake of holding up to 10 GB data? How might this differ with the .mdb structure? Does SQL Server leverage the same file formats/associations?

What would I have to re-learn? I've got so much infrastructure set up in my Access framework (dynamic module processes, PDF printers, etc) -- would I be able to still use all this stuff if I switch to SQL Server Express?

I find myself hitting the 2 GB limit pretty frequently with a few of my backends, so I want to split them up. But how can I tell which things to split off first?

See thread title.

Is there a good, automated way to do this?

Is this accurate in general: Backend: Tables only Frontend: Linktables, queries, forms, macros, etc. So if I have another frontend and I need to, say, edit information in the backend tables, do I just link, again, straight into that backend? Can someone explain the logic of always using...

I have an automated process that iterates through a list of maketable queries and executes them, and if there's an error, it logs it. The problem is that if, for any reason, the query can't execute properly, I still lose my table if I try to run MakeTableQueryA but MakeTableQueryA fails. I...

Right now I am using a temporary table as my recordset, but I want this to be something a bit more dynamic. How would I set the recordset's source buttons in the form to something that creates created/deleted on the fly and derived from another recordsource?

I have a form that generates data based on a recordset. I want a user to be able to change values and then press a Print button. However, I don't want those user changes to be reflected in the underlying data. How can I do this?

My backend is too large to put into only one file unfortunately

try "AgreedCostType like " instead of "AgreedCostType="

Okay so I wrote a function that extracts the name of the table from an append query so I can run a delete from table command beforehand: Private Function getTableNameFromQuery(query As String) As String Dim qry As DAO.QueryDefs Dim db As DAO.Database Dim i As Integer Set db = CurrentDb Set...

Furthermore, is there a way to change a maketable into an append query while also extracting the table dest from that query? It's going to be a huge pain otherwise, since it goes from: running "maketableA" query to running "delete from some table referenced via maketableA before" + running...

Right, but my question is about how this would all look with the fe/be structure and linked tables. Would I need to refer to the be database in my queries if I am deleting/inserting from a frontend? For example, would it be something like this: Windows scheduler kicks off fe.mdb fe.mdb...

So I would have to do each one with two commands? First delete from table, then append? I can indeed do that instead -- but I am still confused about the general structure of all this, regardless.

Why? 10char

What would a sample setup be at the most basic level? Say we have the following as an example: 1. External dbf files, ext1.dbf and ext2.dbf that get dumped from another application (no control over this) 2. Backend DB, be.mdb 3. Frontend DB, fe.mdb I want to: -Create table1 via maketable...

So generally the backend is nothing BUT data and nothing more? No queries, forms, functions, etc? Is there any speed slowdown to doing it split? So the queries would basically look like "select * from [thisdatabase].[this table] and insert into etc"? What if the frontend only has one copy via a...

Ah, my bad. XD Sorry for not being more accurate with my problem. Thanks!