Search results

You can use a "empty" parameter query and simply define the SQL as you go. No need to hard code it. You could in fact store the SQL strings in a table and use string manipulation to replace holders for the criteria operators? That would make the queries themselves data driven. Whether it is...

No you can't. Consider this SELECT Blobby From TABLE1 Where CNum > [@YourParameterValue] Against SELECT Blobby From TABLE1 Where CNum "> [@YourParameterValue]" Can you see why it won't work? It doesn't understand the second one, as it's not a valid SQL statement.

Your query def should be > [SortOrderCriteria] You can't bodge the ">" into the parameter - it's declared as a long, and wouldn't work as a string. So in the query simply place the > in front of the parameter holder and save it.

It can be very useful for simple things to avoid creating them in a query. One of the best examples would be concatenating FirstName and LastName fields into a calculated FullName field , also Initials , as they are frequently used.

In your source queries try the following Eval([Forms]![PowerBI_Export_Pop_Up_Form]![Text2]) and see if they suddenly work.

The parameterised query is by far the best way to handle potential character issues. Imagine passing in a password - something like d£t%"_ u|?''p5= The parameterised query handles it seamlessly. Replacing things would almost certainly fail to handle this in most cases, and obscures what is...

I have assumed it's an Excel Table not a linked table, and I'm sure the same applies when using formulas. There is no such thing as a Null value as far as Excel formulas are concerned. It doesn't have an intrinsic IsNull formula operator. A null cell may have a formula in it bizzarely...More...

You must set the form border style to dialog, not NONE.

@Pat Hartman - In an Excel cell formula there is no NULL only ever "" when a cell is empty.

2. Set the border style to Dialog. Open it as acDialog , set control box to no, close button to no. Remove the caption.

Just to confuse or conflate matters, I had this happen to me ages ago, on Windows 10 - A rogue Access process left behind, after closing a database either manually or in code. I never got to the bottom of it (tried office repair, remove and reinstall etc. etc. ). I only made it go away when I...

Because the backend is SQL server and your Server table field didn't allow nulls, Access doesn't know about that until it's too late. Table level validation is a pain to use with anything other than an Access table, as Access doesn't apply the rules, the server does. Table level constraints...

You could host the BE Database in Azure SQL Server and maintain your current front end Access application, with suitable modification to allow for the performance difference between the WAN environment and the current LAN set up. I suspect you would need to move quite a lot of the processing...

Not in my experience, it's effectively the same storage, just without the "active" file syncing. It's a good place to distribute a FE from and an awful place to store a BE.

I used to sell car audio equipment - so would happily go down this route, but in my car there is nowhere to fit anything aftermarket. It doesn't have a slot for a radio. It has an 11 speaker active system as standard, digital time correction for the offset left/right stereo balance and you can...

I quite like the steering wheel, and a decent radio/sound system.

VAG, BMW and Mercedes have had this model for quite a lot of years. (3 or 4 at least) My wife's' Audi A3 has all the hardware on board for Intelligent (Radar controlled) Cruise control, but we didn't spec it when we ordered it. You can "rent" it by the day, month, year or forever if you want to...

Further discussion / Cross-posted here https://techcommunity.microsoft.com/discussions/Access/ssma-for-access-not-recognising-datetimeextended-fields/4442520 For information I'm using version 10.2

It's a office update thing. I had a client panicking about it about 3 weeks ago, thinking they had broken something.

An ArchivedDate flag is something I use extensively in a lot of tables. It makes it easy to manage historic data and keep data entry forms relative to the live environment. IMHO there is nothing intrinsically wrong with displaying a Autonumber ID as a unique reference as long as no relevance...