Search results

@Gemma: A365 doesn't exist, I just checked. @ Spike: the problem is that there are so many version of Office 2013 that I don't know which one to chose. And notice that the store is now the only way you can get details on any given package...

@Spike Yes, I am talking about A2013 that comes with Office 365 personal. You are talking about a A2013 full version: at MS, no one seems to know the existence of such a package...

I now have the reason behind those problems. Office 365, which contains A2013, is causing the problem. It has to be used connected to the web to get any help, that is rotten anyway - most of the time I have to search the web to get MSN descriptions. A2013 is made to use web data files. It is a...

Attached is a possible and ugly solution to your issue. One major problem with your DB schema is that your records are not uniquely defined. So I am proposing a suffix to make the records unique. Of corse there is an other possibility: a quote table, a subquote table and then the quotes records...

No, no keep the PK. I just forgot a tiny detail: to avoid duplicates add, before the .edit On Error Resume Next and after the .Update On Error Go To Erreur (I am francophone...) a standard error treatment bloc. the tables may have the same quote number for two or more states. So you have to...

Make sure that ModifiedRecords has ony one field QuoteNum as a PK. This to avoid duplicates if there is more than 1 mismatch in any given pair of record.

@vbaInet #9: that's YOUR opinion, but you omit the fact that my solution works without any mods. In his post he uses 'the user' not 'the users'. @SlimJen1 Where and what is the error??? It works fine on my A2013. What are you using? Here is a union query that you will use for a mismatch...

Well M. KnowsItAll, can you give an example of AutoNumber failure? I think you are just an arrogant bubble mouth...

Create a table that will hold the 1...22 corresponding value. From that table, create a combo with 2 col.: 1) 1...22, 2) corr. number. In the AfterUpdate event of this combo fetch col(1) value and store it in the appropriate field.

pbaldy gives you the solution for Access usage. For the Excel data, I would import them into an Access table. Not knowing the structure of Excel data I can't go further but there is a solution to this issue... By the way, I am using Access for 20 years and I never had any problems with...

Are you comfortable with VBA? Because using VBA there is a very easy solution to your issue. I just checked the link old... of jdraw and the solution is right there...

Here is a simple (well it's already created and tested) solution to your issue:;) Public Function Comparaison() Dim rstA As Recordset, rstB As Recordset, rstT As Recordset Dim str As String Dim I As Integer, J As Integer Set rstA = CurrentDb.OpenRecordset("CurrentData")...

Attached is MY version of your issue solution. Of course, you will find strange mods but take the time to examine their signification. Note the somewhat complexity of handling actual stock without keeping it in a table (read JDraw link). Any question can be sent as PM. Good luck, JLC.

@Lejano08: The job waiting for you is complex: is there anyone you know who is familiar with server? Get cool with LOL: I asked you Server OS? PCs OC? Access version? Spike is kind of rough but he is wright: if you don't answer to question, you will discourage any help...

@Gina It as nothing to do with splitting an app: when MS decided to drop the User Level Security, they were leaving the Access app creators to handle it themselves. Nice job. I made a huge system for DomFer using A97 (1999-2008), controlling the hole operations of the plant (approx. 1400...

Galaxiom: what automation has to do with form/subform design? I always use the form/subform design because they are natural: invoice/items, etc.

I can't offhand think of an example of this but you know that the error will need some action. Are you a clairvoyant?:rolleyes:

And you're welcomed! Server OS? PCs OC? Access version? Be very attentive when reading a reply: I gave you a solution. So, decide on an auto update of the FE (I used 12:15AM) and run a scheduled job, installed on every PC, that updates the local FE. Of course, the batch file needs to be...

OK. Here is a procedure that will always work. 1- Make sure that all the annullable field are present on the form but invisible i.e. stored in an invisible form footer. 2- When annulation is triggered, put some code that sets them to null. 3- Add a docmd that will force save the record. That...

I totally missed than ribbon stuff: thanks to remind me.