Search results

The UK or to be more accurate the Media and Reporting from the UK has become almost as polarised as the US. It is very difficult to find neutral reporting. A lot of it is clickbait headlines, and biased. We do still have free speech, contrary to some reports, but in too many circumstances we...

Just as a warning: That only works with an Access back end. The ID isn't committed with a SQL Server BE until the update is carried out.

If this works: 48: ((36/48)*(([Yards]*36)*[Inches])/1296) Then you correctly added the format in the second version 48: Format( ((36/48)*(([Yards]*36)*[Inches])/1296) , "0.000") So not sure why the second version didn't work.

I think you misunderstood me. I know it will be valid until you issue .Update Store the value at the start of the insert: Dim NewID as Long rs.AddNew NewID = NUOVO_VALORE_DA_GENERATORE_GLOBALE() ''' This will store the new value rs("ID_FERICEVUTE") = NewID Call...

When you issue rs.update the recordset doesn't stay on that record. Assuming your NUOVO_VALORE_DA_GENERATORE_GLOBALE() function retrieves the next ID simply store that in a variable at the beginning of the process.

Buy out Google?

I think the effect is far more noticeable / undesirable within the Access ecosphere we inhabit, as developers we tend to leverage the ability to control Outlook a lot more than a majority of traditional users of of Word, Excel and PowerPoint do. In my experience, even complex spreadsheet...

Welcome aboard Zoe!

Sorry, this is just wrong - indexes won't help with very badly stored data. It's like putting a small band-aid on a broken leg.

If you pulled all the station data into one table with an couple of identifier fields for the Building and floors, you would only need then link that to your station team data. You team data should be in a separate table referencing the location. Something like

I would just set those values as the default values on the form controls. When you then go to a new record they will be the values in those fields, no need for the insert statement at all.

That looks very much like very poorly stored data, and I suspect would benefit from being correctly normalised. Any time a table name or field name looks like it is holding data e.g. Haus1 , Haus2 etc. it probably shouldn't be in a separate table but identified by a field with the table...

If this is just displaying existing data then use your MySQL database to generate the row number, why would you try and do it locally when there is inbuilt functionality in the back end DB? If you are simply adding a line item then the sequence number will be 1 more than the last one for that...

We support in excess of 40 databases of various sizes that are hosted in Azure SQL with Access front ends. Whist it will never be as quick as a local SQL backend, if it is carefully designed the "slowness" is minimal, and with sensible planning can out perform a local Access backend...

Azure has a cost but it varies tremendously depending on what you set up. ~£50 a month gets you a scalable, resilient Cloud based SQL server for a basic system, with redundancy and backups. I don't think that's a lot. ~£200 a month gets you something you could run most medium/larger sized...

If any of the destination and source tables have an Identity (Autonumber) field it would fail, however I would expect it to tell you that as the error message, not one about MV fields?

If the fields being updated are indexed then the index also needs updating, which when it involves millions of records can take a considerable amount of extra time. When doing enormous updates it can be beneficial to drop, update, and then recreate the indexes.

If you simply set the control default value to Date it will only apply to new records, unless there is something more complicated going on here.

Try the following Forms!Form0_AddEditJob!TBOX_DateInitial.DefaultValue = "= Date() "

If you are doing this dynamically on a continuous form (e.g. up/down arrows for example), you only ever need to move the item up or down one position, so you only need to adjust the previous or next item in the list and replace their sort order with the original. It makes it much simpler.