Search results

I'm trying to think of when you might want a relationship but not use RI. I guess maybe to improve join performance while ignoring orphans?

Yes it should but then there are lots of things that the SSMA does now that it once didn't. FYI: while following your advice to remove explicit indexes where an implicit index already exists for a FK, I found one interesting anomoly. When trying to delete one index (in table design view) I got...

Tip: for testing you can use the Developer edition of SQL Server rather than Express. It's free but has all the functionality of a paid edtion, it's just the license does not allow for its use in production.

What? Why wasn't I told? so I just iterated the index collection of a table and looked at the fields and you are correct! Thanks for this enlightenment, I'll stop adding extra indexes for FKs in Access dbs. apparently the Access team decided that indexes on FKs are essential and I would agree...

When 365 went all subscription on us, the Business plans did not include Access. Only the Enterprise plans did, then after a couple of years MS realised their mistake and added Access to the Business plans. Hence the confusion.

Yes most of us know that date time is a number, left of the decimal point is date, right is the time (at least in Access and VBA not so much in SQL Server which uses two integers). But here we are only concerned with the integer Date Value and how the UI deals with it and converts it to that...

If only it were that simple. The control knows it is a date from its format property, be it short date or whatever. Type in "2/1" and you get 02/01/2024 The issue is that that the Format Condition does not recognise it as a date regardless of the control's format property or does not respect...

Only seems to be an issue comparing dates in unbound controls Typically this is used for Report Criteria Bound controls act as advertised resolved by using Expression Is: Format([txtStart_Date],"yyyymmdd")>Format([txtEnd_Date],"yyyymmdd") Version 2311 Build 17029.20140 Region > Format: English...

Is this issue related to ANSI 92 compatibility? and will changing this resolve the issue? It did seem to in the sample accdb I created and George sent to you when I updated to 2311. Note to others: you won't find this setting in Options for Current Database, it's in the Object Designers tab

OK, I've got the same issue with a combo box. based on a table with 2 columns and only 2 rows. 365 Enterprise 32 bit, accdb in Windows 11 I've even copied a known good combo box from another application and changed the rowsource. Problem persists Tried changing the setting for this application...

The simple answer is Public Sub ReplaceInSQL() Dim qdf As DAO.QueryDef Dim strFind As String Dim strWith As String strFind = "Whatever" strTo = "Whichever" Set qdf = CurrentDb.QueryDefs("QueryName") With qdf .SQL = Replace(.SQL, strFind, strTo) End With End Sub...

The simple solution is to share responsibility for testing with your client or the project manager. With the client having responsibilty for the final testing. I don't release a new version, they do. They must have a critical process test plan that they go through to ensure that there will not...

@Jackoo6 - this is the link to Geroge's post with a link to the video Migrating tables to SQL Comparison

Are you in a multi user environment? ie are you sharing your database with other users? If not then LarryE's suggestion will suffice. The only problem with this solution is, if you have multiple users working on the same table. Users' selections can be affected by each other's selections. A...

Must agree that a Deleted Date and Deleted By column is the ideal. Then filter your record sets to Where Deleted Date Is Null. When users complain that data has gone missing and, as the developer, it's your fault, you can show them why and even recover it.

Users should all be using their own copy of the Front End, so they should all currently have an ADP. You should be working on an accdb that you will give to everyone else once you've got it working and tested. So in the mean time other users should not be affected. The MAIN difference is that...

When I create a table in SS from VBA, I create the table with just the PK strSQL = "CREATE TABLE dbo." & strTableName _ & " (" & strFieldName _ & " INT IDENTITY(1,1) NOT NULL" & vbNewLine _ & " CONSTRAINT " &...

KMan, I had a similar experience except that it was with combo boxes not text boxes. This was on a single record view, unbound form. I removed and recreated to fix the issue. But then I had crashes on another (Continuous form). again, combo boxes. After much addoo, wailing, nashing of teeth...

@Jike Krailo "There are many DB's that will never have the need to move to sql server." very true, I was attempting to provide Pros as well as Cons but will admit I'm a bit biases against attachments, or any other non conforming data type, because I spend much of my time migrating the...

arenpg is correct. If you can, keep the file external to the db and only store the file name (or full path) in the table. But you will need to save the file to a location that all users can access. storing the image as an attachment in the db bloats the db and the attachment data type is not...