Search results

When I move my access databases to a new server, a lot of the code breaks on-run. For instance: Microsoft Office xx.0 Object Library PDFCreator Is there a way I can programatically remove bad references and re-add the good ones across all my databases?

Basically I have everything formatted in my report except the actual values (I've got column text headers going across representing C1, C2, C3, and row text headers going down representing R1, R2, R3, etc) So I have a table, T, that actually has all the values I want to pull onto this report...

Sigh, still a problem. Using the gamma function isn't precise. To find 6!, using that gamma expression gives me 719.999999862944 which makes me unable to differentiate between a whole integer answer (6! being 720) and a decimal answer to begin with. AGHHHHH. Why can't Excel use a better...

Okay I think I've got it. I can replace the ( with EXP(1)^GAMMALN(1+ so you can write fact(x) as EXP(1)^GAMMALN(1+x) Not sure if this'll help anyone else, but alas...

I found one solution that uses x*exp(1)^gammaln(x) but it doesn't work for x=0, argh. I need a way to basically apply this to a string replace. For instance, I might have str="5+(4+5)" and I want to be able to replace the ( with fact( so I get "5+fact(4+5)" Problem is sometimes the input is...

Sorry, I meant facty. Slip of the tongue. Factout is a separate factorial function I have but it suffers from the same problem. Facty was chosen arbitrarily out of the two. Edited the original post.

The reason why I need to custom-make the fact() function is because Excel's fact() accepts decimals as valid inputs and I want it to only return values when the inputs are whole numbers, say fact(0) or fact(10) but not fact(2.2). Fact(2.2) truncates the decimal whereas I need it to not do so.

So I know there's a fact() function but bear with me -- there's a reason why I need to use a user-made function, here, but I don't need to get into it. But I am using the following: Function facty(expression As Variant) As Variant Dim I As Double Dim bNum As Variant If...

I don't either, but it's beyond my control -- hence my inability to figure out a good way to handle this. I know that the new table would basically include the relevant data from Customers in addition to new, defaultly-blank Send fields. The problem is how to properly append/modify this table...

Because the Send fields are new fields that don't currently exist in Customers, and the Customer table is already being used in a ton of other integrations/manners and I'd rather not potentially botch something. Customers itself is a part of a maketable process and I don't know how to put...

Background info: Cust_ID represents the id number of a customer, Branch is the general location (e.g. "Dallas"), Representative is the person assigned to that customer, and Address is the customer's address. SendMail, SendEmails, and SendCalls are boolean values that basically ask "Is it OK to...

The current network of databases is very automated and has many interlinkages -- exporting systems and so forth that have export paths listed as elements within tables and so forth. But since this will need to go to a new server, all sorts of links will need to be updated. It's not a system I...

Is there an easy way to do mass-replacements within tables in the same way as queries?

The code works but it always seems to hang on the following For Each qdf in Currentdb.QueryDefs strSQL = qdf.SQL for large queries Basically I am moving a bunch of Access DBs to a new server and I need a way to update any hardlinks that may exist (relink tables, any links in-queries...

For large queries, that routine takes forever. Is there any way to just edit the SQL without needing to "execute" it on the backend to get all its properties when I run code? ALL I want to do is be able to mass-replace things in the SQL in a flash.

Is there a way to cycle through all queries in my db without needing the name?

For instance, say I have a bunch of queries like so: select a, b from [pathway to db.mdb].RandomQuery and I want to programatically change them to this: select a, b from [a new pathway.mdb].RandomQuery

Say I have a pre-existing Excel file (with desired print formatting/settings), and I just want to port a remote query into that file template and export it somewhere. I need to be able to leverage queries that may be in other databases.

What is the quickest and most effective way to do this? Say I have a database, a.mdb. It has a query inside of it, MainQuery. I want to be able to take the contents of MainQuery from a.mdb and then export it to Excel format. I also need to not kick off any startup macros/automations that...

The purpose of the tables is to fuel other queries/reporting procedures/export functions. They're just recreated everyday because the raw data changes from day to day, and Access is the medium in which such reporting is conducted. A delete-and-insert approach would accomplish the same thing...